PA500 Restart Reason Log

Announcements

Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

Reply
Si_Infrastructure
L1 Bithead

PA500 Restart Reason Log

I am trying to determine why a PA500 firewall was rebooted...i ran this command: tail mp-log masterd.log and got the below. I couldn't find any references for the restart reasons. How do i know if there was a power outage? Thoughts?

 

2018-11-28 13:37:13.158 -0500 INFO: l3svc: received user restart
2018-11-28 13:37:13.172 -0500 INFO: l3svc: User restart reason - restart triggered by devsrvr commit
2018-11-28 13:37:13.194 -0500 INFO: l3svc: received user stop
2018-11-28 13:37:17.419 -0500 INFO: l3svc: exited, Core: False, Exit code: 0
2018-11-28 13:37:18.309 -0500 INFO: l3svc: process running with pid 11847

OtakarKlier
Cyber Elite

Hello,

What version are you running? Looks like there was a bug fix in 7.1.5.

 

Fixed an issue where a process (devsrvr) restarted repeatedly due to a problem with the internal URL cache structure.

 

Regards,

Si_Infrastructure
L1 Bithead

Hello,

 

we're runnining 8.0.10

 

Do you know where I can find a reference for the reboot reasons?

 

Thanks.

OtakarKlier
Cyber Elite

Hello,

I would suggest just searching the knowledge base.

 

Regards,

Gustavo_Aristi
L1 Bithead

This is a bit of a late response but someone might find it useful later.

 

If this is an HA configuration, you can find the restart reason under the ha_agent.log

 

Gustavo_Aristi_0-1601925600230.png

 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!