XmlException Syntax Error

[kcasante]

I wish there were instructions this good on how to solve this for freenas users.
I reported this issue way back at the beginning of the thread. I was able to use the “pkg mono update” command to get it updated. BUT everytime sonarr has an update it breaks it again. This morning I’m seeing the same mono 3.1.0 again. This time that command does nothing.
This issue has been plaguing me for months now. So frustrating…

[kcasante]

I ran into this error on freenas 11 using the Sonarr plugin version 2.0.0.3732 PBI sonarr-2.0.0.3732-amd64.

pkg install mono was upgrading the system mono, but sonarr wasn’t updating because it was using its own mono binary:

# cat /usr/local/etc/rc.d/sonarr | grep mono
procname="/usr/pbi/sonarr-amd64/bin/mono"

I switched that procname in the start up script /usr/local/etc/rc.d/sonarr:

# cat /usr/local/etc/rc.d/sonarr
#!/bin/sh
#
# Author: Mark Felder <feld@FreeBSD.org>
#
# $FreeBSD$
#

# PROVIDE: sonarr
# REQUIRE: LOGIN
# KEYWORD: shutdown

# Add the following lines to /etc/rc.conf to enable sonarr:
# sonarr_enable="YES"

. /etc/rc.subr

name="sonarr"
rcvar=sonarr_enable

load_rc_config $name

: ${sonarr_enable="NO"}
: ${sonarr_user:="sonarr"}
: ${sonarr_data_dir:="/usr/pbi/sonarr-amd64/sonarr"}

pidfile="${sonarr_data_dir}/nzbdrone.pid"
procname="/usr/local/bin/mono"
command="/usr/sbin/daemon"
command_args="-f ${procname} /usr/pbi/sonarr-amd64/share/sonarr/NzbDrone.exe --nobrowser --data=${sonarr_data_dir}"
start_precmd=sonarr_precmd

sonarr_precmd()
{
	export XDG_CONFIG_HOME=${sonarr_data_dir}

	if [ ! -d ${sonarr_data_dir} ]; then
		install -d -o ${sonarr_user} ${sonarr_data_dir}
	fi
}

run_rc_command "$1"

I was then getting a SIGSEGV related to my sqlite install. I removed my system version of sqlite3 (sqlite3-3.23.1) and downgraded to sqlite3-3.13.0 and then restarting sonarr got everything back up and running correctly again:

root@sonarr_1:~ # pkg delete -f sqlite3
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:
	sqlite3-3.23.1

Number of packages to be removed: 1

The operation will free 5 MiB.

Proceed with deinstalling packages? [y/N]: y
[sonarr_1] [1/1] Deinstalling sqlite3-3.23.1...
[sonarr_1] [1/1] Deleting files for sqlite3-3.23.1: 100%
root@sonarr_1:~ # fetch "http://pkg.freebsd.org/freebsd:11:x86:64/release_0/All/sqlite3-3.13.0.txz"
sqlite3-3.13.0.txz                            100% of  677 kB 1071 kBps 00m00s
root@sonarr_1:~ #
root@sonarr_1:~ #
root@sonarr_1:~ # pkg add sqlite3-3.13.0.txz
[sonarr_1] Installing sqlite3-3.13.0...
[sonarr_1] Extracting sqlite3-3.13.0: 100%

Hopefully this helps

This worked for me as well.
I would add for Freenas users that aren’t well versed in the command line. (Took me a while to find the instructions on how to edit the file in freenas ssh)
To edit the /usr/local/etc/rc.d/sonarr script you just have to go to that directory and type:
edit sonarr

The editor is pretty self explanatory.

Also after I did this I was able to get sonarr to jump to mono 5.2.0 but now within the freenas gui it looks like the sonarr service is off and it won’t start. I’ve tried clicking on it, and I’ve tried “service sonarr onestart” from ssh. Sonarr is actually running fine but for some reason I can’t get freenas gui to turn the service on.

I’m not sure if that’s why @cholly did the sql reinstall (I didn’t bother with that because after updating the script and a reboot sonarr started right up and the mono had changed) and Frankly if this is how it has to be so I don’t have to worry about sonarr dropping the mono on me; I’ll take it. Thanks @cholly for the explanation and the instructions to get this fixed; Much appreciated.

[veridian5]

Will there be a patch to address this? Seems a lot of people having the same issues.

[Taloth]

@veridian5 we only provide packages for windows, debian/ubuntu and to some extend osx. Packages for other platforms such as freebsd, qnap, archlinux, unraid etc are provided by third parties and are outside of our control.
It basically boils down to an outdated mono version, not something we can ‘patch’ Sonarr for.

[veridian5]

Ok I see. Thanks for the update.

Steps to fix on Freenas:

• Ssh into freenas
• Run warden list to get the list of jails
• Jexec <nameofsonarrjail>
• Pkg install mono
• Edit the config file here /usr/local/etc/rc.d/sonarr
• Change the procname address to:
• procname="/usr/local/bin/mono"
• Restart the jail