updated murmur now complains about segmentation fault

[Grasfer]

Hi, updated murmur from murmur: 1.2.8_1 -> 1.2.10 and now when i try to start it it complains about segmentation fault.

root@server:/ # service murmur start
Starting murmur.
Segmentation fault
/usr/local/etc/rc.d/murmur: WARNING: failed to start murmur

Never got a error like that before so no idea where to start. Started googling but only found people with broken usb's/boot devices. Got my jails on a dedicated SSD.

Tried removing and reinstall but still same error.

Code:

The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        openssl: 1.0.2_4

Installed packages to be UPGRADED:
        murmur: 1.2.8_1 -> 1.2.10

The process will require 11 MiB more space.
3 MiB to be downloaded.

Proceed with this action? [y/N]: n
root@server:/ # service mumble stop
mumble does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d)
root@server:/ # cat /etc/rc.conf
portmap_enable="NO"
sshd_enable="NO"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
hostname="server"
devfs_enable="YES"
devfs_system_ruleset="devfsrules_common"
inet6_enable="YES"
ip6addrctl_enable="YES"
murmur_enable="YES"
znc_user="znc-admin"
znc_enable="yes"
znc_conf_dir="/usr/home/znc-admin/.znc"
nginx_enable="YES"
php_fpm_enable="NO"
mysql_enable="NO"
syslogd_enable="NO"
syslogd_program="/usr/sbin/syslogd"
syslogd_flags="-ss"
root@server:/ # service murmur stop
Stopping murmur.
Waiting for PIDS: 7737.
root@server:/ # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (2 candidates): 100%
Processing candidates (2 candidates): 100%
The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        openssl: 1.0.2_4

Installed packages to be UPGRADED:
        murmur: 1.2.8_1 -> 1.2.10

The process will require 11 MiB more space.
3 MiB to be downloaded.

Proceed with this action? [y/N]: y
[server] Fetching murmur-1.2.10.txz: 100%  390 KiB 400.2kB/s    00:01
[server] Fetching openssl-1.0.2_4.txz: 100%    2 MiB   1.4MB/s    00:02
Checking integrity... done (0 conflicting)
[server] [1/2] Installing openssl-1.0.2_4...
[server] [1/2] Extracting openssl-1.0.2_4: 100%
[server] [2/2] Upgrading murmur from 1.2.8_1 to 1.2.10...
You may need to manually remove /usr/local/etc/murmur.ini if it's no longer needed.
==> You should manually remove the "murmur" user.
===> Creating users and/or groups.
Using existing group 'murmur'.
Using existing user 'murmur'.
[server] [2/2] Extracting murmur-1.2.10: 100%
Message from openssl-1.0.2_4:
Copy /usr/local/openssl/openssl.cnf.sample to /usr/local/openssl/openssl.cnf
and edit it to fit your needs.
root@server:/ # service murmur start
Starting murmur.
Segmentation fault
/usr/local/etc/rc.d/murmur: WARNING: failed to start murmur
root@server:/ # cat /etc/rc.conf
portmap_enable="NO"
sshd_enable="NO"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
hostname="server"
devfs_enable="YES"
devfs_system_ruleset="devfsrules_common"
inet6_enable="YES"
ip6addrctl_enable="YES"
murmur_enable="YES"
znc_user="znc-admin"
znc_enable="yes"
znc_conf_dir="/usr/home/znc-admin/.znc"
nginx_enable="YES"
php_fpm_enable="NO"
mysql_enable="NO"
syslogd_enable="NO"
syslogd_program="/usr/sbin/syslogd"
syslogd_flags="-ss"
root@server:/ # updatedb
>>> WARNING
>>> Executing updatedb as root.  This WILL reveal all filenames
>>> on your machine to all login users, which is a security risk.
root@server:/ # locate murmur.ini
/usr/local/etc/murmur.ini
/usr/local/etc/murmur.ini.sample
root@server:/ # service murmur start
Starting murmur.
Segmentation fault
/usr/local/etc/rc.d/murmur: WARNING: failed to start murmur
root@server:/ # service murmur start
Starting murmur.
Segmentation fault
/usr/local/etc/rc.d/murmur: WARNING: failed to start murmur
root@server:/ # pkg remove murmur
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        murmur-1.2.10

The operation will free 1 MiB.

Proceed with deinstalling packages? [y/N]: y
[server] [1/1] Deinstalling murmur-1.2.10...
You may need to manually remove /usr/local/etc/murmur.ini if it is no longer needed.
==> You should manually remove the "murmur" user.
[server] [1/1] Deleting files for murmur-1.2.10: 100%
root@server:/ # pkg install murmur
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        murmur: 1.2.10

The process will require 1 MiB more space.

Proceed with this action? [y/N]: y
[server] [1/1] Installing murmur-1.2.10...
===> Creating users and/or groups.
Using existing group 'murmur'.
Using existing user 'murmur'.
[server] [1/1] Extracting murmur-1.2.10: 100%
root@server:/ # service murmur start
Starting murmur.
Segmentation fault
/usr/local/etc/rc.d/murmur: WARNING: failed to start murmur

 

[SweetAndLow]

Looks like a bad build of murmur, did you see any issues with that release when doing a search?

 

[Grasfer]

Looks like a bad build of murmur, did you see any issues with that release when doing a search?

Not yet, atleast nothing useful on google, gonna try install older version for now if i figure out how to.

 

[SweetAndLow]

For testing purposes many create a new jail and do a fresh install using the newest current murmur version. Maybe something in the upgrade went bad.

 

[Grasfer]

For testing purposes many create a new jail and do a fresh install using the newest current murmur version. Maybe something in the upgrade went bad.

Good idea, i'll try that tonight or tomorrow after work. Found my previous version(1.2.8_1) and installed that and it started fine.