John Hodrien wrote:
Is monitoring working in 0.3? If so, is there a guide for setting it up
lurking about?
Well it is there. But since there has been massive changes in paths, do
not expect it work. You are guinea pig now. Please report it as bug. If
you have solution even better.
I've just upgraded 0.2 -> 0.3, enabled monitoring through the web interface
then starting poking. It seems to have installed rather oddly as a
result of
having ~nocpulse=/home/nocpulse from a previous install.
I'm sorry. Did not have time to test it on upgrades yet. I'm sooo much
happy that Monitoring can even start now.
For now I suggest to remove all Monitoring packages and nocpulse user
and install that new packages (not upgrade).
After sorting that out, gogo.pl:185 looks wrong to me, so I changed
NotificationQueue to NOCpulse::NotificationQueue.
Fixed in master.
Then it failed because perl-Class-MethodMaker from EPEL was v2 and doesn't
appear to be backwards compatible. So I installed a v1 release.
I did not hit this bug. Please fill in bug.
Then there were a bunch of missing directories in /etc/nocpulse that it
complained about, and a missing ini file. Then some more missing
directories
in /var/lib/nocpulse.
The same. I did not hit this bug. Please fill in bug.
But this looks it is related to the upgrade.
After all that's sorted, the Monitoring service starts without errors.
I have been here on last Thursday.
MonitoringScout is a different story. It pauses at NPbootstrap after
failing
to access:
https://spacewalk-server.mydomain/satconfig/cgi-bin/fetch_netsaintid.cgi
This is where I'm currently, did not had progress on this this week.
I plan to point nightly builds to dist-5E-sw-0.4-candidate and when I
will do it, you can upgrade monitoring packages from there.
--
Miroslav Suchy
RHN Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
