New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu Server 22.04.1 LTS VM - WebOne v0.12.3 fails to start with Exit Code 131 #76
Comments
So, at the moment, I got a Windows 10 VM running and also installed WebOne there. That worked just fine. Was able to configure my proxy settings on my retro machines through there. But for whatever reason, the Linux distros that I've tried so far (CentOS 7, Ubuntu Server 22.04.1 LTS, and Xubuntu 22.04 LTS) has not worked for me at all. Once again, they were clean OS installs with WebOne downloaded and configured afterwards. Even followed the Linux install instructions. No dice. |
@dg410a please try this to change webone.service like the following #75 (comment) and then systemctl enable webone |
What if run WebOne as regular app, not a service? Does it starts or returning an error? |
@way5 Configuring webone.service as suggested did not work. @atauenis Actually did run webone as normally and got this:
I even tried wget to download the .NET runtime as indicated above to see if I could fix it, but got a 301 at first before it timed out. Though strangely enough, the apt package manager DID recognize and install NET 6.0 alongside WebOne as seen below:
So, my guess is that somehow, the path configurations were not set up properly in order for this to work right out of the box. |
Just got it to work.
EDIT: Nevermind. Recent attempts to reproduce this to find the cause just ended up with the same previous errors again with WebOne refusing to work at all. EDIT 2: So... I followed the Linux instructions again to install WebOne and did a system restart. Afterwards, the program now works as normally. Service is still not functional though. EDIT 3: After further testing, WebOne even fails to start on boot when using crontab or rc.local. |
Tried on my VM with Ubuntu 22.04 .0 , everything is working correctly. The VM haven't updated from approximately June. Now I've attempted to install all updates (simply
Reinstall ( Seems that it is a bug of updated Ubuntu .NET packages. Maintainers has broken something. Interesting that .NET 7.0 installs correctly. But it's not LTS and have no support for Windows pre-10, so there are currently no plans on updating to .NET 7 (probably WebOne will go to .NET 8 when .NET 6 became out of support). |
Continuing investigation.
May be creation of some links in system will solve? |
Found a solution:
The 6.0.8 version of .NET Runtime is working great on Ubuntu 22.04.1, unlike 6.0.11. |
Can confirm that this solution works 100%. Although, I had to refer to here in order to get 6.0.8 to even install. The default apt repository for 22.04.1 would not download the earlier version unless if I configure it to use the PMC feed for NET 6.0. Only then was I able to install 6.0.8 without any issues. |
Good news. Microsoft has released the 6.0.12-1 Runtime where the bug is fixed. But Ubuntu repositories still have 6.0.111 version (6.0.11 rebuilt by Canonical), so the package version holding still need.
|
Good news! Canonical pushed For test, I've reinstalled Ubuntu 22.04.1 from scratch, then downloaded On existing systems Microsoft considers remove packages.microsoft.com repository from system, purge |
I have WebOne installed on an Ubuntu Server 22.04.1 LTS virtual machine. Didn't install anything else other than the program alongside the dependencies used to run it. WebOne version is v0.12.3.
It will NOT start at all, even after configuring my own settings for "DefaultHostName" and "Port".
Here is the output from the "sudo service webone status" command:
Before this, I also tried it on a clean CentOS 7 install with the same results. This leads me to believe that this particular package may be broken or that there is something else missing beyond what I've tried.
The text was updated successfully, but these errors were encountered: