#NABox3 dc ps Rebooting

1 messages · Page 1 of 1 (latest)

heavy perch
#

Hi Team,

We are seeing that the services are rebooting in the NAbox 3

Can you please help me on this

Thank you

IMG_3121.jpg
winged sinew
#

@wheat bay

wheat bay
#

What's the available capacity ?

#

AH that's NAbox 3. Maybe the watchdog going cookoo

#

systemctl stop nabox-api-watchdog (IIRC)

#

Could be worth checking dc logs -f nabox-api

heavy perch
#

Im not sure why im getting this error as in picture 1

wheat bay
#

What was the command ? a simple cat ?

#

probably naboxd restarting and rewriting the config file

heavy perch
heavy perch
wheat bay
#

Looks like it's being restarted from outside

heavy perch
wheat bay
#

Try service nabox-api-watchdog stop

heavy perch
wheat bay
#

mmm... It's not stopping ?

heavy perch
#

It’s recreating again and again

wheat bay
#

killall -9 nabox-api-watchdog

heavy perch
#

I still see process

wheat bay
#

it's the grep

#

I think you're fine now

#

dc up -d in case not everything is up

heavy perch
#

Yes everything is up since last 2 minutes

wheat bay
#

ok you can start the watchdog again I believe

heavy perch
heavy perch
wheat bay
#

Try service nabox-api-watchdog start

heavy perch
#

O started and got output as attached

#

Everything is up since last 6 minutes

wheat bay
#

welll.... seems good then

#

thoughts on moving to nabox 4 ?

heavy perch
#

Thanks a lot @wheat bay it was a really quick and very helpful response

wheat bay
#

Well, I have my moments 😄

heavy perch
wheat bay
#

And that's because NAbox 3 let you customize aleerting more than NAbox 4 ? Because of the read only partition ?

heavy perch
wheat bay
#

All right I need to prioritize this

heavy perch
wheat bay
#

what's the file you are modifying ?

#

alertmanager.yml ?

#

or individual rules ?

heavy perch
#

Yes

#

Alert manager

wheat bay
#

I think you can already find alertmanager.yml in /etc/nabox/alertmanager, and change it

heavy perch