You are not logged in.

#1 2019-01-17 02:49:27

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Hi All,

I just updated my system however after checking my apache server running an ASP.net website (mod_mono module) after this I get a 503 error.

Checking the apache error log I get the following: "Failed to connect to mod-mono-server after several attempts to spawn the process".

I checked my conf file to see if the file path and the file path still seems valid:

MonoServerPath "/usr/bin/mod-mono-server4"

Also updated to the latest version of mod_mono in the AUR, still nothing. Also tried downgrading apache which was updated with no luck.

Anyone have any suggestions or know how to solve this?

Many Thanks

Offline

#2 2019-01-17 22:42:43

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Ok so turns out it will work after a while. Httpd spawns about 4-5 threads that all max out the core they are running on when the system is started. Then followed about 10-15 minutes later by some mod-mono-server ones which eventually stop..

Anyone have any idea what is going on??

Last edited by doctorzeus (2019-01-17 22:43:12)

Offline

#3 2019-01-22 03:49:05

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Seems there is an issue here:

https://github.com/mono/mod_mono/issues/9

However no reply from the developers or anyone and it has existed since October last year!

Also any server-side code doesn't work at all and after fiddling around the applications seem to now give a permanent 503 error.. sad

Offline

#4 2019-02-02 03:46:34

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

So I did a complete system downgrade to the following packages and everything works fine again! Currently trying to figure out which package is the culprit:

iana-etc-20180913-1-any.pkg.tar.xz
filesystem-2018.8-1-x86_64.pkg.tar.xz
tzdata-2018g-1-x86_64.pkg.tar.xz
ncurses-6.1-4-x86_64.pkg.tar.xz
readline-7.0.005-1-x86_64.pkg.tar.xz
bash-4.4.023-1-x86_64.pkg.tar.xz
pcre-8.42-1-x86_64.pkg.tar.xz
libutil-linux-2.33-2-x86_64.pkg.tar.xz
glib2-2.58.1+67+g17519e039-1-x86_64.pkg.tar.xz
gdbm-1.18.1-1-x86_64.pkg.tar.xz
libsystemd-239.303-1-x86_64.pkg.tar.xz
e2fsprogs-1.44.4-1-x86_64.pkg.tar.xz
avahi-0.7+16+g1cc2b8e-2-x86_64.pkg.tar.xz
bc-1.07.1-2-x86_64.pkg.tar.xz
libxml2-2.9.8-6-x86_64.pkg.tar.xz
python-3.7.1-1-x86_64.pkg.tar.xz
libidn2-2.0.5-1-x86_64.pkg.tar.xz
lmdb-0.9.22-1-x86_64.pkg.tar.xz
bind-tools-9.13.5-1-x86_64.pkg.tar.xz
bind-9.13.5-1-x86_64.pkg.tar.xz
binutils-2.31.1-3-x86_64.pkg.tar.xz
python-msgpack-0.5.6-2-x86_64.pkg.tar.xz
python-pyparsing-2.3.0-1-any.pkg.tar.xz
borg-1.1.7-2-x86_64.pkg.tar.xz
libpsl-0.20.2-1-x86_64.pkg.tar.xz
curl-7.63.0-1-x86_64.pkg.tar.xz
device-mapper-2.02.183-1-x86_64.pkg.tar.xz
diffutils-3.6-2-x86_64.pkg.tar.xz
fuse-common-3.3.0-1-x86_64.pkg.tar.xz
fuse3-3.3.0-1-x86_64.pkg.tar.xz
gawk-4.2.1-1-x86_64.pkg.tar.xz
tar-1.30-2-x86_64.pkg.tar.xz
gzip-1.9-2-x86_64.pkg.tar.xz
guile2.0-2.0.14-2-x86_64.pkg.tar.xz
gdb-common-8.2-2-x86_64.pkg.tar.xz
gdb-8.2-2-x86_64.pkg.tar.xz
gnutls-3.6.5-1-x86_64.pkg.tar.xz
sqlite-3.26.0-1-x86_64.pkg.tar.xz
libsecret-0.18.6-1-x86_64.pkg.tar.xz
gnupg-2.2.12-1-x86_64.pkg.tar.xz
graphite-1:1.3.12-1-x86_64.pkg.tar.xz
grep-3.1-2-x86_64.pkg.tar.xz
guile-2.2.4-1-x86_64.pkg.tar.xz
libpng-1.6.35-1-x86_64.pkg.tar.xz
harfbuzz-2.2.0-1-x86_64.pkg.tar.xz
http-parser-2.8.1-1-x86_64.pkg.tar.xz
inetutils-1.9.4-6-x86_64.pkg.tar.xz
iproute2-4.19.0-1-x86_64.pkg.tar.xz
iputils-20180629.f6aac8d-2-x86_64.pkg.tar.xz
libcups-2.2.10-1-x86_64.pkg.tar.xz
libedit-20180525_3.1-1-x86_64.pkg.tar.xz
libwbclient-4.9.3-1-x86_64.pkg.tar.xz
linux-firmware-20181216.211de16-1-any.pkg.tar.xz
pcre2-10.32-1-x86_64.pkg.tar.xz
shadow-4.6-1-x86_64.pkg.tar.xz
util-linux-2.33-2-x86_64.pkg.tar.xz
systemd-239.303-1-x86_64.pkg.tar.xz
linux-4.19.9.arch1-1-x86_64.pkg.tar.xz
lua52-5.2.4-3-x86_64.pkg.tar.xz
lvm2-2.02.183-1-x86_64.pkg.tar.xz
man-db-2.8.4-1-x86_64.pkg.tar.xz
pacman-5.1.1-1-x86_64.pkg.tar.xz
python2-2.7.15-2-x86_64.pkg.tar.xz
s-nail-14.9.11-1-x86_64.pkg.tar.xz
smbclient-4.9.3-1-x86_64.pkg.tar.xz
samba-4.9.3-1-x86_64.pkg.tar.xz
sed-4.5-1-x86_64.pkg.tar.xz
sshfs-3.5.0-1-x86_64.pkg.tar.xz
sssd-2.0.0-1-x86_64.pkg.tar.xz
sudo-1.8.26-2-x86_64.pkg.tar.xz
systemd-sysvcompat-239.303-1-x86_64.pkg.tar.xz
unixodbc-2.3.7-1-x86_64.pkg.tar.xz
wget-1.19.5-1-x86_64.pkg.tar.xz
xfsprogs-4.19.0-1-x86_64.pkg.tar.xz
apache-2.4.33-3-x86_64.pkg.tar.xz

Last edited by doctorzeus (2019-02-02 23:11:57)

Offline

#5 2019-02-02 15:52:42

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,701

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Can I get you to please edit your post and surround that list with BBCode code tags?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#6 2019-03-02 05:02:30

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

So after a VERY VERY long process of debugging I finally found why my system is doing this.

It seems after upgrading past systemd and systemd-sysvcompat version 239.303 this starts happening. Seems very bizarre that the problem is with systemd! Stab in the dark maybe there is something to do with some new systemd security patch or new feature?

Considering this new information can anyone theorize (or better wink ) on why this would be happening please?

I understand mod_mono is probably a bit of a niche plugin with linux users but hopefully someone out there has had the same problem!

Many Thanks

Last edited by doctorzeus (2019-03-02 05:04:53)

Offline

#7 2019-04-28 06:16:21

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

This is still an issue and after searching the internet recently I have still not been able to find a solution.

The most recent update makes systemd and systemd-sysvcompat 239.303 have issues with the device manager configuration.

Since there is no clear path as no one seems to know what is going on with this the only thing I can see to do is to switch our test server web applications to .net core. But this seems like a ridiculous length to have to go to just for a bug.

Offline

#8 2021-01-21 16:05:10

Potomac
Member
Registered: 2011-12-25
Posts: 513

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

The bug is still here in january 2021, has anyone found a workaround ?

Or the best solution is to switch to .Net core with apache ?

Last edited by Potomac (2021-01-21 16:06:26)

Offline

#9 2021-01-22 04:32:56

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Potomac wrote:

The bug is still here in january 2021, has anyone found a workaround ?

Or the best solution is to switch to .Net core with apache ?

The problem is that mod_mono and xsp (which mod_mono utilizes) has not been maintained for quite some time (since April 2018) and I don't expect it to change unless someone picks up the project..

I would also not recommend using it in any sort of PROD or wan-facing environment as there could be any number of security holes..

A workaround however is to enable the proxy module in apache and then forward to an xsp server running the app on a local port. As you mentioned though best thing to do is to convert to dotnet core but just know that it cant run ASP.NET web applications so you need to convert.

Offline

#10 2021-02-03 10:53:31

obones
Member
Registered: 2019-04-11
Posts: 1

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Potomac wrote:

The bug is still here in january 2021, has anyone found a workaround ?

Here I did two things:

1. configure mod_mono to use a TCP port
2. run mod-mono-server manually with the same TCP port

Point 2 could be made into a service to have it started automatically.

I'm not sure this is "viable" for the long term, but at least it allows me to see my internal mono based web dashboard.

Offline

#11 2021-02-03 12:03:56

Mardukazs
Banned
Registered: 2021-02-02
Posts: 5

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Potomac wrote:

The bug is still here in january 2021, has anyone found a workaround ?

Or the best solution is to switch to .Net core with apache ?

You're hosting older ASP.NET under mono under apache? Just... why and how? How did you get here? Why you thought that was anything but insane? Are you running production... under mono? With apache? Holy crap batman. Mono had the speed of ruby or python scripting languages, why would anyone chose ASP.NET over scripts when not deploying on Windows Server?

Every sane person does this: self hosting .NET 5 (or .NET Core 3.1 if you want LTS release) behind nginx reverse proxy. That's like the default .NET deployment.

---

Apache is like slow and clunky and deprecated and used for php to deploy wordpress e-shops to 1 dollar webhosts via ftp or whatever. It's not 2006 anymore, really.

Last edited by Mardukazs (2021-02-03 12:07:39)

Offline

#12 2021-02-03 14:25:31

doctorzeus
Member
Registered: 2011-12-24
Posts: 74

Re: Apache (mod_mono) Error After Upgrade - Failed To Spawn Process

Mardukazs wrote:
Potomac wrote:

The bug is still here in january 2021, has anyone found a workaround ?

Or the best solution is to switch to .Net core with apache ?

You're hosting older ASP.NET under mono under apache? Just... why and how? How did you get here? Why you thought that was anything but insane? Are you running production... under mono? With apache? Holy crap batman. Mono had the speed of ruby or python scripting languages, why would anyone chose ASP.NET over scripts when not deploying on Windows Server?

Every sane person does this: self hosting .NET 5 (or .NET Core 3.1 if you want LTS release) behind nginx reverse proxy. That's like the default .NET deployment.

---

Apache is like slow and clunky and deprecated and used for php to deploy wordpress e-shops to 1 dollar webhosts via ftp or whatever. It's not 2006 anymore, really.

I kind of a assumed he was doing it for a personal experiment and had already been through this nightmare..

My OP was actually for a test we were doing on a dev server for a VERY specific client requirement on what was then a legacy site we were upgrading..

Offline

Board footer

Powered by FluxBB