Skip to main content ↑ ↓
Topic: cant find log file for crashed daemon (Read 1533 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

cant find log file for crashed daemon

Hi, im starting the openrc script for syncthing (from galaxy/syncthing-openrc).
Then i do rc-service syncthing status, and i get status: crashed.
However, im unable to find a log file that gives me an actual message. Should i assume there is a log somewhere? nothing in /var/log
Also, the program works fine without the openrc unit, im having trouble with this. How do i debug this.

Re: cant find log file for crashed daemon

Reply #1 –
ok, there is progress, it seems i can use a system logger (syslog-ng)  and then it gives me an actual error:

Mar 30 01:29:44 artix /etc/init.d/syncthing[7168]: start-stop-daemon: no matching processes found

could there be a problem with the openrc script?

Re: cant find log file for crashed daemon

Reply #2 –
more progress, im having a blast 8)

it was actually dumb of me to assume the service would start as my main user where all the config files are. I used printf to debug and looked at some variables:

Code: [Select]
start() {
  ebegin "Starting syncthing"
#-  printf "${SYNCTHING_USER}\n\n\n\n${SYNCTHING_ADDRESS}LLLLL\n\n\n\n${SYNCTHING_ARGS} \n\n\n"
  start-stop-daemon --start --make-pidfile --pidfile /run/syncthing.pid \
    --background --user ${SYNCTHING_USER} --name syncthing \
    --exec /usr/bin/syncthing -- -gui-address=${SYNCTHING_ADDRESS} ${SYNCTHING_ARGS}
  eend $?
}


should i just edit SYNCTHING_ADDRESS, SYNCTHING_ADDRESS and SYNCTHING_ARGS in this file or is there a better way to do it?
im not sure why those variables have a value even though they are never assigned.

edit: it works now, btw, just wondering what to do about those variables, and should i run the service as my regular user, should i even edit this file, and general good way to do this