Bug 277930 - www/owncast: not starting after the update to 0.1.2
Summary: www/owncast: not starting after the update to 0.1.2
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
: 277931 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-24 19:55 UTC by gnunix
Modified: 2024-03-26 09:06 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (de-freebsd)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gnunix 2024-03-24 19:55:55 UTC
Owncast (www/owncast port) doesnt seem to want to start after update to 1.0.2.

Runs fine when i install the package version owncast: 0.0.13_4, starts with no problem but with the new port it seems to not be able to read the pidfile in /var/run, as shown here:



/usr/local/etc/rc.d/owncast: DEBUG: pid file (/var/run/owncast.pid): not readable.

command run:

service owncast start
/usr/local/etc/rc.d/owncast: DEBUG: pid file (/var/run/owncast.pid): not readable.
/usr/local/etc/rc.d/owncast: DEBUG: checkyesno: owncast_enable is set to YES.
/usr/local/etc/rc.d/owncast: DEBUG: run_rc_command: doit:  owncast_start
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2024-03-24 21:39:56 UTC
*** Bug 277931 has been marked as a duplicate of this bug. ***
Comment 2 gnunix 2024-03-26 09:06:07 UTC
After reading the debug.log it seemed that the port doesnt set the user and group of the /usr/local/www/owncast directory right, setting these with 

chmod -r owncast:owncast /usr/local/www/owncast solved my issue.


Mar 25 16:07:25 de4dcpu owncast[26073]: time="2024-03-25T16:07:25+01:00" level=fatal msg="Cannot set up emoji directory unable to create custom emoji directory: mkdir data/emoji: permission denied"
Mar 25 16:07:50 de4dcpu owncast[26121]: time="2024-03-25T16:07:50+01:00" level=error msg="stat data/emoji: permission denied"



Issue solved.