tentacle problem

[rnovoa]

Like it

Up

0

Down

Drop it

::

Hi,

hello fellow pandora user’s,

I downloaded the following VMware image:
PandoraFMS 1.3.1
Ubuntu8.04 server
a week ago. so far its the best freeware monitor tool I have seen and I’m very excited to implant this app, But at the moment I’m stuck :(.
and hoping you guys can help me out.

tentacle server wont start for some reason, when I start up the server it comes whit the following error:
[code:1][err] cannot read /dev/null: permission denied
Tentacle server could not be started
* running local boot script (etc/rc.local)

Sounds like /dev/null was created with the wrong permissions. Could you run the following commands as root and tell us if tentacle_serverd goes up? Thanks!

[code:1]
chmod 666 /dev/null
/etc/init.d/tentacle_serverd start

In the file:
/usr/share/pandora/util/tentacle_serverd

I changed the TENTACLE_ADDR= to my server ip.

Make changes to /etc/init.d/tentacle_serverd instead, this is the one that gets called at startup :).

Furthermore the sendmail isnt working, how can i configure sendmail under ubuntu to use my internal mail server as relay?

Thanks in advance,

Pieter Koppert

[stellingwerf-college]

Like it

Up

0

Down

Drop it

::

Thanks,

chmod 666 /dev/null
/etc/init.d/tentacle_serverd start

Now the tentacle service started, but still not at boot. If i run chmod after booting again its starting correctly again.
Furthermore i now edited the /etc/init.d/tentacle_serverd 😉

[rnovoa]

Like it

Up

0

Down

Drop it

::

Thanks,

chmod 666 /dev/null
/etc/init.d/tentacle_serverd start

Now the tentacle service started, but still not at boot.If i run chmod after booting again its starting correctly again.

That problem with /dev/null is weird, must be an udev issue. As a workaround you could try editing /etc/init.d/tentacle_serverd and inserting the line:

[code:1]
chmod 666 /dev/null

before the call to sudo. I am not sure when /dev/null permissions get changed, but it could work 🙂

Furthermore i now edited the /etc/init.d/tentacle_serverd 😉

[stellingwerf-college]

Like it

Up

0

Down

Drop it

::

Thanks for the input!

Your workaround helped, i figured out the source of the problem.
My eth0 device was not working in the vmware image. The pandora wiki stated that i should run sudo rm /etc/udev/rules.d/*.*
Unfortenatly that also removes the file where the /dev/null rights get set at boot.

executing only sudo rm /etc/udev/rules.d/70-persisent-net.rules is sufficient. To solve eth0 problem.
Is it possible to add this to the wiki?

Regards,

Pieter

[manu]

Like it

Up

0

Down

Drop it

::

True

Added!
Thanks