This did it for me too. Thank you so much for solving this. Now I can fresh start with Netedit and the most recent Debian underlaying.
Original Message:
Sent: Feb 24, 2025 01:53 PM
From: cm119
Subject: NetEdit service not starting after updating debian to version 11
Update, we got this fix for the service startup issue. Seems to be working so far.
sudo systemctl mask postgresql
sudo reboot
Original Message:
Sent: Feb 05, 2025 07:11 PM
From: cm119
Subject: NetEdit service not starting after updating debian to version 11
Did you get this resolved? I have been having the same issue, it's apparently a bug with newer versions, the wrong database starts up on startup and uses the TCP port so that the correct service fails to start. I'm waiting for an answer on the bug fix.
You can try this:
sudo systemctl stop postgresql@14-main.service
sudo systemctl start postgresql-svr.service
sudo systemctl start netedit-svr.service
Original Message:
Sent: Oct 31, 2024 02:55 AM
From: JN20
Subject: NetEdit service not starting after updating debian to version 11
Hey guys,
I just did a fresh install of netedit on VM vSphere hypervisor. The deployment went fine and I was able to access NetEdit afterwards.
Then I updated the underlaying Debian with apt-get update and apt-get upgrade.
After a reboot the NetEdit service is not willing to start anymore.
This is what I get on the console:
● netedit-svr.service - NetEdit application server service
Loaded: loaded (/etc/systemd/system/netedit-svr.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-10-30 23:23:20 PDT; 1min 21s ago
Process: 1640 ExecStart=/opt/netedit/bin/netedit-start.sh (code=exited, status=0/SUCCESS)
Main PID: 1648 (code=exited, status=1/FAILURE)
CPU: 36.940s
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.postgresql.Driver.makeConnection(Driver.java:402)
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.postgresql.Driver.connect(Driver.java:261)
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.springframework.jdbc.datasource.SimpleDriverDataSource.getConnectionFromDriver(SimpleDriverDataSource.java:144)
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnectionFromDriver(AbstractDriverBasedDataSource.java:20>
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnection(AbstractDriverBasedDataSource.java:169)
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: at org.flywaydb.core.internal.jdbc.JdbcUtils.openConnection(JdbcUtils.java:48)
Oct 30 23:23:19 vesvi1266 netedit-start.sh[1648]: ... 30 common frames omitted
Oct 30 23:23:20 vesvi1266 systemd[1]: netedit-svr.service: Main process exited, code=exited, status=1/FAILURE
Oct 30 23:23:20 vesvi1266 systemd[1]: netedit-svr.service: Failed with result 'exit-code'.
Oct 30 23:23:20 vesvi1266 systemd[1]: netedit-svr.service: Consumed 36.940s CPU time.
Does anyone have a clue how to get NetEdit running again?