[olug] Murmur in Fedora 16
Sam Flint
harmonicnm7h at gmail.com
Fri Dec 30 15:06:20 UTC 2011
Just as in Apache run murmurd as user murmur
-- Sam Flint,
Have a happy Hannukah!
On Dec 29, 2011 11:19 PM, "T. J. Brumfield" <enderandrew at gmail.com> wrote:
> Murmur is an open source voice chat server like Teamspeak or Ventrillo.
>
> It has a pre-packaged sqlite that comes with it. The documentation says you
> shouldn't need to do anything, as it should just work out of the box. And
> as this is a shipped package with Fedora, I'd assume the package should
> mostly work out of the box.
>
> I can make the file writable by a non-root user, but I'm not sure what user
> the daemon should end up running as. Non-root users don't have access to
> the log file, and it won't start as root. The service bundled with the
> Fedora package is an old init script, not one of the new systemd scripts.
> I'm wondering if I just need to update it.
>
> It seems like the shipped package won't even start out of the box. Fedora
> doesn't have any additional documentation for Murmur on their end, and the
> official Murmur documentation hasn't been very helpful.
>
> I was curious if anyone on the list has either run Murmur, or converted an
> old init script to a new systemd script for Fedora 16.
>
> On Thu, Dec 29, 2011 at 10:05 PM, Dan Linder <dan at linder.org> wrote:
>
> > I don't know what "murmurd" does, so I'll apply some generic
> > troubleshooting questions:
> > > <C>2011-12-12 09:02:26.891 Successfully switched to uid 993
> > > <F>2011-12-12 09:02:26.912 ServerDB: Failed initialization: unable to
> > open
> > > database file Error opening database
> >
> > Are the DB communication strings setup properly? Is the DB started
> > and listening on the port as "murmurd" expects (i.e. encryption
> > settings, authentication, etc)? Is the "UID 993" able to connect to
> > the DB port (it's possible SELinux or other security tool is
> > restricting it)?
> >
> > > I can start murmurd as a non-root user, but then I get an error that it
> > > can't write to /var/log/mumble-server/mumble-
> > > server.log
> >
> > That's probably because the file (mumble-server.log) and/or the
> > directory (/var/log/mumble-server/) are not writable by the non-root
> > user. If you delete the .log file, then "chmod a+rwx
> > /var/log/mumble-server/", the non-root user should be able to use it.
> >
> > Dan
> >
> > --
> > ***************** ************* *********** ******* ***** *** **
> > "Quis custodiet ipsos custodes?"
> > (Who can watch the watchmen?)
> > -- from the Satires of Juvenal
> > "I do not fear computers, I fear the lack of them."
> > -- Isaac Asimov (Author)
> > ** *** ***** ******* *********** ************* *****************
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > https://lists.olug.org/mailman/listinfo/olug
> >
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>
More information about the OLUG
mailing list