ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003001ClearOSapp-print-server - CUPS Print Serverpublic2015-05-29 09:242015-07-30 08:59
Reporteruser2 
Assigned Touser2 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version7.1.0 Beta 3Fixed in Version7.1.0 Beta 3 
Summary0003001: Cups init script can corrupt ClearOS API
DescriptionWhatever part of the init script that is used in the CUPS start script to determine what interfaces to listen on (eg. generates cupsd.listen.conf) can corrupt the ClearOS API (/network/library/Iface.php becomes a socket!).

Looks like an exception is being thrown, and instead of handling the exception, the script is looping through the content/backtrace and adding to the cupsd.listen.conf file. Eg:

# Automatically generated by init script
Listen PHP:631
Listen warning::631
Listen fopen(/sys/class/net/eth10/device/subsystem_vendor)::631
Listen failed:631
Listen to:631
Listen open:631
Listen stream::631
Listen No:631
Listen such:631
Listen file:631
Listen or:631
Listen directory:631
Listen -:631
Listen /usr/clearos/apps/network/libraries/Iface.php:631
Listen (1116):631
Listen PHP:631
Listen warning::631
Listen fopen(/sys/class/net/eth10/device/subsystem_device)::631
Listen failed:631
Listen to:631
Listen open:631
Listen stream::631
Listen No:631
Listen such:631
Listen file:631
Listen or:631
Listen directory:631
Listen -:631
Listen /usr/clearos/apps/network/libraries/Iface.php:631
Listen (1125):631
Listen PHP:631
Listen warning::631
Listen fopen(/sys/class/net/eth11/device/subsystem_vendor)::631
Listen failed:631
Listen to:631
Listen open:631
Listen stream::631
Listen No:631
Listen such:631
Listen file:631
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0001611)
bchambers (administrator)
2015-05-29 10:12

No upgrades found:

[root@- cups]# rpm -qv app-network
app-network-1.6.10-1.v6.noarch


This server was a Community -> Pro upgrade earlier, if that makes any difference.

- Issue History
Date Modified Username Field Change
2015-05-29 09:24 user2 New Issue
2015-05-29 09:24 user2 Status new => assigned
2015-05-29 09:24 user2 Assigned To => user2
2015-05-29 09:24 user2 Issue generated from: 0002991
2015-05-29 09:24 user2 Target Version 7.1.0 Beta 2 => 7.1.0 Beta 3
2015-05-29 10:12 bchambers Note Added: 0001611
2015-06-15 19:41 user2 Status assigned => resolved
2015-06-15 19:41 user2 Resolution open => fixed
2015-07-28 10:16 user2 Status resolved => closed
2015-07-30 08:59 user2 Fixed in Version => 7.1.0 Beta 3