errorlog
(1) By decuser on 2023-01-07 00:17:11 [source]
I'm moving from running in inetd to running direct as a daemon in freebsd in preparation for running in a jail on Truenas Core. As part of the process, I'm trying to get it log stuff.
The command I'm using in my rc file boils down to:
/usr/local/bin/fossil server -P 8080 --repolist /zfs/fossils --errorlog /var/log/fossil.log
The command seems to work (fossil gets served), but I'd like some reassurance that it will log stuff. I tried going to a non-existent page "http://localhost:8080/c45/homer" and got:
Not Found
Page not found: homer
but nothing appears in the log file.
Does anything look wrong with my command, what kind of logging should I expect to see, and can I generate an error to see there?
- will
(2) By Stephan Beal (stephan) on 2023-01-07 00:29:14 in reply to 1 [link] [source]
what kind of logging should I expect to see,
Only fatal errors, IIRC.
Visit /secaudit0 as an administrator and it will tell you info about the error log, including reporting an error if it cannot write to that file. Just search that page for "errorlog" and you'll see it.
(3) By decuser on 2023-01-07 00:34:21 in reply to 2 [link] [source]
Thanks for that. I get:
The server error log at "/var/log/fossil.log" is -1 bytes in size.
Unable to open that file for reading!
I tried not creating it first and then tried touching it.
(4) By decuser on 2023-01-07 00:51:46 in reply to 3 [link] [source]
Figured out how to get stuff in fossil.log:
/usr/local/bin/fossil server -P 8080 --repolist /zfs/fossils --errorlog fossil.log
then the log shows up relative to the repolist directory in /zfs/fossils/fossil.log
I get errors, but I'll ask that in a separate thread. This one's solved.
(5) By decuser on 2023-01-07 16:02:26 in reply to 1 [link] [source]
Ultimately, the real fix was to properly install as noted in this thread (7.1):