killall majestic
ulimit -c unlimited
echo /tmp/%e.%p.%s.%t.core > /proc/sys/kernel/core_pattern
majestic
Core dump file from /tmp/ , e.g. /tmp/majestic.806.11.1619707881.core
Issue description
A brief description of the problem. Should include what you were
attempting to do, what you did, what happened and what you expected to
see happen.
Majestic doesnt reload properly when receiving the kill -1 HUP signal. It is my understanding that whenever a config value is changed i the HUP signal is sent and majestic reloads.
No changes have been made to replicate this issue. Default majestic.yaml config. Send kill -1 and it will not load again. Some majestic web UI pages (port :85) will show 500 Internal Server Error
All works fine on first boot.
Expectations
Majestic to successfully reload on config change/ HUP signal
Steps to reproduce
Step one
Boot camera
Step two
get PID from ps aux | grep majestic
Step three
Send HUP signal with kill -1 <PID>
Step four
Load a Majestic settings page on webUI port 85 and see 500 Internal Server Error
Information to attach
[ ] Any relevant log output (logread -f)
Running killall majestic and manually starting mjaestic in the foreground. Then sending kill -1 signal from another window shows these logs:
Required information
Issue description
A brief description of the problem. Should include what you were attempting to do, what you did, what happened and what you expected to see happen.
Majestic doesnt reload properly when receiving the kill -1 HUP signal. It is my understanding that whenever a config value is changed i the HUP signal is sent and majestic reloads.
No changes have been made to replicate this issue. Default majestic.yaml config. Send kill -1 and it will not load again. Some majestic web UI pages (port :85) will show 500 Internal Server Error
All works fine on first boot.
Expectations
Majestic to successfully reload on config change/ HUP signal
Steps to reproduce
Step one Boot camera
Step two get PID from
ps aux | grep majestic
Step three Send HUP signal with
kill -1 <PID>
Information to attach
logread -f
)Running
killall majestic
and manually startingmjaestic
in the foreground. Then sendingkill -1
signal from another window shows these logs:cat /etc/majestic.yaml
) [Default]