Notes |
|
|
This error has ocurred in many installations. |
|
|
|
Please attach the /var/log/raa/raa-service.log file. |
|
|
|
Some windows that are not available are:
Configuration
Configure Networking
System Time
Maintenance
Logs
Manage Services
Updates
View and Apply Rollbacks
The log we get is the following:
The traceback is:
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/raa/vendor/CherryPy-3.0.3/cherrypy/_cprequest.py", line 551, in respond
File "/usr/lib64/python2.4/site-packages/raa/vendor/CherryPy-3.0.3/cherrypy/_cpdispatch.py", line 24, in __call__
File "/usr/lib64/python2.4/site-packages/raa/web/__init__.py", line 274, in inner_wrap
ret = func(*args, **kwargs)
File "/usr/lib64/python2.4/site-packages/raa/web/__init__.py", line 223, in inner_expose
return func(*args, **kw)
File "/usr/lib64/python2.4/site-packages/raa/authenticate.py", line 82, in inner_require
return func(self, *args, **kwargs)
File "/usr/lib64/python2.4/site-packages/raaplugins/services/web/services.py", line 221, in index
statuses = self.callBackend('getServiceStatuses', [x[0] for x in srvs])
File "/usr/lib64/python2.4/site-packages/raa/modules/raawebplugin.py", line 516, in callBackend
triggerImmed(schedId)
File "/usr/lib64/python2.4/site-packages/raa/modules/raawebplugin.py", line 38, in triggerImmed
client.connect( cfg.listenerFile )
File "<string>", line 1, in connect
error: (111, 'Connection refused') |
|
|
|
OK. Please download and attach the "Agent service" and the "Agent web service" log files from the machine that this happened. |
|
|
|
The files have been downloaded after restar raa becuase the log were not available. |
|
|
|
I have face a similar problem when launching the backup process. See attach backup.png. For some reason the console doesn't work and i have to reboot the console. After this I can do the backup.
The week before I could make the backup and i didn't do anything during the week after and suddenly when I try to execute the backup didn't work. It seems like the console stopped working without doing anything |
|
|
|
More things:
After rebooting the console /etc/init.d/raa restart, the system suddenly shutdown itself without doing anything
Very, very strange |
|
|
|
Some progress: the issue has been reproduced and it's being analyzed by us and rPath. |
|
|
|
There is a candidate fix for this, setting the pieURL to http and port 8004 in raa_service.conf. Currently the user's feedback have been positive. So we'll wait for 1 week to see if any issue is raised. |
|
|
|
To be fixed in the upcoming 2.40MP4 release. |
|