Computer pr0n

murmurd 1.2.5

by on Feb.17, 2014, under How-to, Linux, Software

loclhst

Announced a few weeks ago, version 1.2.5 of the mumble client and server were released. There were a few security fixes and they urge everyone to upgrade.

By the request of a few of my readers, I have created the .spec and .rpm for my implementation for 1.2.5!

If you are running my version of the 1.2.3a instance, I suggest checking out my last post on the upgrade process to 1.2.4.

If you are running my version 1.2.4 instance, well then read on, because the upgrade is even simpler this time!

As noted last time, the .spec file is located on my github at https://github.com/drdelaney/custom-rpm-spec and EPEL is still required for this install as well.

New installation

After verifying that you have the EPEL repo installed, just install the RPM!

[root@server ~]# yum --nogpgcheck --enablerepo=epel install http://files.loclhst.com/mumble/1.2.5/mumble-server-1.2.5-DrD.i386 investigate this site.rpm
...
Installed:
  mumble-server.i386 0:1.2.5-DrD

Complete!

Setting up the super password for the first time

[root@server~]# /usr/local/sbin/murmurd -ini /opt/mumble-server/mumble-server-default.ini -supw <new password>

Now start the server

[root@server ~]# /etc/init.d/mumble-server start
Starting mumble-server:                                    [  OK  ]

At this time, you may need to punch a hole in the firewall.

This setting will vary from system to system, but for common firewall settings, this should work

[root@server ~]# iptables -A INPUT -p tcp -m tcp --dport 64738 -j ACCEPT
[root@server ~]# iptables -A INPUT -p udp -m udp --dport 64738 -j ACCEPT
[root@server ~]# /etc/init.d/iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[  OK  ]
[root@server ~]# /etc/init.d/iptables restart
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Unloading modules:                               [  OK  ]
iptables: Applying firewall rules:                         [  OK  ]



Upgrading from 1.2.4

make sure you have a backup of your working configuration!

Stop the server and Backup!

[root@server ~]# /etc/init.d/mumble-server stop
Shutting down mumble-server:                               [  OK  ]
[root@server ~]# tar czvpf /tmp/mumble124-$(date +%Y%m%d).tar.gz /opt/mumble-server/
tar: Removing leading `/' from member names
/opt/mumble-server/
/opt/mumble-server/mumble-server-123upgrade.sqlite
/opt/mumble-server/logrotate-mumble-server
/opt/mumble-server/weblist.pl
/opt/mumble-server/LICENSE
/opt/mumble-server/mumble-server-123_old.ini
/opt/mumble-server/weblist.php
/opt/mumble-server/mumble-server.ini.example
/opt/mumble-server/README
/opt/mumble-server/murmur.pl
/opt/mumble-server/icedemo.php
/opt/mumble-server/dbus-mumble-server.conf
/opt/mumble-server/Murmur.ice
/opt/mumble-server/mumble-server-default.ini

Upgrade the RPM

[root@server ~]# yum --nogpgcheck --enablerepo=epel upgrade http://files.loclhst.com/mumble/1.2.5/mumble-server-1.2.5-DrD.i386.rpm
...
Updated:
  mumble-server.i386 0:1.2.5-DrD

Complete!

Start the server and test

[root@server ~]# /etc/init.d/mumble-server start
Starting mumble-server:                                    [  OK  ]

Now after the installation or upgrade, make sure to connect your client to the server to make sure things [still] work.

That should be all there is.  If you run into any issues, drop a comment with the error, and I will try to help!

Starting service at system startup

If you want the service to start upon server startup/reboot, then add to the rc init system

[root@server~]# chkconfig --add mumble-server

The mumble server should now start automatically!

Updated 02/18/2014 – Adding in command for first time supw setting and firewall rules

:, , , , ,

20 Comments for this entry

  • Wowakan

    First I want to say great on the new 1.2.5 murmurd install. I was thinking though that for folks that are just installing this as a new server that you might want to add in “How to setup the password”/usr/local/sbin/murmurd -ini /opt/mumble-server/mumble-server-default.ini -supw PASSWORD.

    Second I was looking here “http://mumble.sourceforge.net/Obtaining_a_StartCom_Certificate”
    on getting a Certificate. Do we just fallow this per-quoted or is there a different way with your DrD?

    • loclhst
      loclhst

      Thanks for the recommendation! I added in the supw setting as well as common firewall settings. As for the SSL cert, I have not tried this, but it looks straight forward, and no modifications should be needed, since this is handled from the mumble client side.

    • loclhst
      loclhst

      I went to try for the SSL cert myself, and I got a SSL verification warning in Firefox. I personally do not like this fact and would not suggest using this cert company. As a side note, there is absolutely nothing wrong with using a self-signed certificate. I just ran through the “Create a new certificate” wizard in a matter of seconds.

  • Wowakan

    Well I finally got those parts to working. I am now trying to get Ice on Centos 6.5 to work so I can get the web Interface to work.

  • marksie1988

    Hi,

    Quick question, I want multiple Murmur instances as i have a few clans, is this possible? if so how?

    Steve

    • loclhst
      loclhst

      I plan to implement something in the next RPM to handle starting multiple daemons as needed, but in the mean time, you can use the following information as needed.

      At this point in time, you will not be able to use my init script to do this, but you can write a custom shell script to achieve the same thing!

      The first step would be to make sure you have separate .ini files for each instance. They all have to reside under /opt/mumble-server/.
      In each .ini file, you want to make sure you have unique values for at least the port (anything above 1024 should be fine), the database, logfile and the pidfile.

      Once these are created, make sure the core mumble process has been stopped with:
      # sudo /etc/init.d/mumble-server stop

      Next you will need to imitate the database with a new superuser password
      # sudo -u mumble-server /usr/local/sbin/murmurd -ini /opt/mumble-server/new-instance-1.ini -readsupw

      Now you will need to start the instance
      # sudo -u mumble-server /usr/local/sbin/murmurd -ini /opt/mumble-server/new-instance-1.ini

      Do this for each instance. You can script this out. If you need to kill the servers, you can use
      # sudo kill -TERM $(cat /opt/mumble-server/new-instance-1.pid)

      You will probably want to change the name of the ini, pid, and related entries accordingly.

  • int

    Amazing, thank you so much for putting this together! Worked amazingly and saved me a whole lot of trouble!

  • Wowakan

    Is there anyway you could also post on how to do a full uninstall. We had some folks donate a new server and would like to take the mumble server off the old one and put it on the new one.

    Thank you.

    • loclhst
      loclhst

      The commands are:
      # sudo /etc/init.d/mumble-server stop
      # cd /; sudo tar czvpf /tmp/mumble-backup.tar.gz /opt/mumble-server/
      # sudo yum remove mumble-server
      # sudo rm -rf /opt/mumble-server/

      When you go to restore the data (if you are not starting from scratch):
      # sudo yum install /path/to/mumble-server*.rpm
      # sudo /etc/init.d/mumble-server stop
      # (copy the tar file to the new server)
      # cd /; sudo tar xzvpf /tmp/mumble-backup.tar.gz
      # sudo /etc/init.d/mumble-server start

      I will try to remember to note this on the next post on mumble

  • int

    Thanks for this great set of instructions

    Trying to get mumble/murmur to work with TCADMIN (which offers control panel functionality to mumble servers installed). The problem I’m coming across is that TCADMIN expects to find the mumble files in a certain location, whereas they’re placed elsewhere.

    Having spoken with the folks at TCADMIN, I was told:

    When installing murmur, it placed the files there where the other mumble processes can find it. It’s probably in the path environment variable that’s why it finds the file first instead of the one located in its own folder.

    Any ideas on how I would go about fixing this?

    • loclhst
      loclhst

      The easiest way to fix this without changing the RPM is to symlink the binaries to where TCADMIN wants the files. The other way would be to edit the .spec file and rebuild for your needs. Also, what is the path TCADMIN wants the binaries in?

  • Boradan

    Is this installing ice also on centOS?
    I noticed Murmur.ice in the install folder

    • loclhst
      loclhst

      This does not particularly install ice, though it does include the file. I have not personally messed around with it, but it may work out of the box. If it works for you with little modification, let me know and I can incorporate the changes into the next RPM!

  • JBG

    Just a tip for anyone getting tripped up on dependency errors on CentOS 6.5 getting errors like:

    Package db4-devel is obsoleted by db53-devel, but obsoleting package does not provide for requirements

    fix(for the moment):
    yum –nogpgcheck –enablerepo=epel –disablerepo=zeroc-ice install http://files.loclhst.com/mumble/1.2.5/mumble-server-1.2.5-DrD.i386.rpm

  • Boradan

    Any progress on the ‘messing around with Ice’?
    Getting issues when combining CentOS 6.5, Mumble and IcePHP – mostly I think due to the fact that I have WHM/Cpanel ALSO on my server as cpanel uses a non standard way of installing php

  • BBq

    Any chance you will be creating a new install guide for
    murmurd 1.2.7? This security update apparently addresses the Heartbleed issue. http://blog.mumble.info/mumble-1-2-7/

    Thx!

Leave a Reply

 

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!