ClearFoundation Tracker - ClearOS
View Issue Details
0006621ClearOSapp-suvapublic2015-12-03 16:432016-08-29 09:41
bchambers 
bchambers 
normalminoralways
closedfixed 
7.1.0 
7.2.0 
0006621: Suva daemon is not reloadable
Causes exception when response code doesn't come back 0.

Configlet needs to be changed to 'reloadable' => FALSE so that the reset (not reload) parameter is used.
ec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/apps/base/libraries/Daemon.php (485): execute
Dec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/apps/suva/libraries/Suva.php (180): reset
Dec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/apps/registration/libraries/Registration.php (489): set_device_name
Dec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/apps/registration/controllers/registration.php (157): reset
Dec 3 18:34:11 server engine: exception: debug backtrace: GUI (0): reset
Dec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/framework/system/core/CodeIgniter.php (359): call_user_func_array
Dec 3 18:34:11 server engine: exception: debug backtrace: /usr/clearos/framework/htdocs/app/index.php (222): require_once
Dec 3 18:34:11 server engine: exception: error: /usr/clearos/apps/base/libraries/Shell.php (207): Command execution failed. - /usr/bin/sudo /sbin/service suva reload >/dev/null 2>&1

[root@server ~]# service suva reload
Redirecting to /bin/systemctl reload suva.service
Failed to issue method call: Job type reload is not applicable for unit suva.service.


[root@server ~]# service suva restart
Redirecting to /bin/systemctl restart suva.service
No tags attached.
Issue History
2015-12-03 16:43bchambersNew Issue
2015-12-03 17:51user2Statusnew => confirmed
2015-12-07 21:00bchambersAssigned To => bchambers
2015-12-07 21:00bchambersStatusconfirmed => acknowledged
2015-12-07 21:01bchambersStatusacknowledged => assigned
2015-12-07 21:01bchambersStatusassigned => resolved
2015-12-07 21:01bchambersFixed in Version => 7.2.0
2015-12-07 21:01bchambersResolutionopen => fixed
2016-08-29 09:41user2Statusresolved => closed

There are no notes attached to this issue.