Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Errors installing LoggerNet Linux on SuSe


SnowDog Apr 28, 2011 02:58 PM

Trying to install LoggerNet for Linux on SuSe 11.4 with the 2.6.37 kernel, and I am getting these errors:

insserv: script csilgrnet is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script csilgrnet is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script csildep is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script csildmp is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.

and a lot more just like that as the install script runs.

It does install LoggerNet, and the daemon appears to be running. However, I cannot connect to the server.

Has anyone experienced this?

I have successfully installed Loggernet for Linux on a SuSe 11.1 O/S, running 2.6.32 kernel. It worked effortlessly and flawlessly. I'm not sure what is causing the problems on this upgraded OS.


SnowDog Apr 28, 2011 05:59 PM

I'll answer my own question:

The daemon scripts (the ones that reside in /etc/init.d) have a omission:

As supplied, the 'Required-Stop' line has NO TRAILING COLON!

The Line should be:
# Required-Stop:

but all three scripts are missing the colon.

Simply edit 'csildep', 'csildmp', 'csilgrnet' and add the colon. However, Campbell Scientific should provide the correct script in the rpm file, and I hope they make this change before some other dummy like me wastes several hours figuring out the problem.

SnowDog in Montana


Dana Apr 30, 2011 04:00 AM

I've asked one of our product testers to look at this and log an issue. We were working on getting back with you, in response to your direct email to our support email address. Sorry for the delay -- the original email went to another AE in our office, who forwarded it to me, and I was working away from the office yesterday with no email access.

Sorry to have caused you grief.

Regards,

Dana W.

Log in or register to post/reply in the forum.