[Openslp-users] Registrations and server restarts
Brought to you by:
jcalcote
From: Gavin L. <ga...@co...> - 2013-11-20 06:14:13
|
Hi all, I have a fairly simple test network setup at the moment with one Windows machine and four Linux machines running OpenSLP (all with the same code, which is one of the just-immediately-prior-to-release 2.0 betas); and there are no DAs. The four Linux machines all run the same app which is supposed to have a permanent SLP registration. Today I noticed while running an unrelated soak test (so everything had been running for several hours, in some cases days) that two of the four machines were no longer responding with the service info for that app. The app is still running, and slpd is still running. However logs show that (at different times) the slpd service on both of the affected machines shut down and was restarted one second later, for no readily apparent reason. (In particular, the slpd.log appears to show a normal shutdown / startup banner, but there's no other apparent cause for the restart.) The app normally makes a single call to SLPReg on startup with SLP_LIFETIME_MAXIMUM. On rare occasions it'll call SLPReg again to change one or more of its attributes. Only when the app exits does it SLPDereg and SLPClose. No errors were returned from these APIs. So, two points puzzle me: 1. why did slpd restart? 2. why, following the restart, didn't it reload the registration made previously? (For #2, I'm assuming the app shouldn't have to manually refresh the registration since AFAIK it has no way to tell whether slpd has restarted or not.) If the assumption in #2 isn't valid, is there something the app should be doing to keep this registration alive? (Preferably without spamming SLPReg or making it find itself.) |