Serviio

I did a search and found a topic from 2016, but there was no solution. I had 2.0 running under Fedora Linux, I installed 2.1. Now 2.0 nor 2.1 will start. I closed the browser tab I had open for the console, but no go. "lsof -i:23423" returns nothing. Here is the log:

I have no clue as to why it will not start. And yes, I ran the starting script with the -stop option first.

If I'm reading the log correctly, there's something on the network already using the same IP address. But Zip will need to look at this, as that line might be referring to something completely different. But comparing that log to mine, that does seem to be where it's binding to the network address.

The problem is what IP address? It would be great if the log listed the problem address. Not doing so results in a great big guessing game.

Even with DEBUG mode enabled, an actual address was not forthcoming.

Do you have multiple network devices on the computer? Any chance you've configured a static IP on this computer, and something else on the network has the same address, possibly from a DHCP server on the network? I've just never encountered something like this, so trying to cover the possibilities.

Lots of devices on my LAN. All devices, except for the phone and the laptop, are issues static IPs. The laptop is DHCP configured for an IP within the DHCP allocated range. I just looked at the router's list of attached devices and there are no duplicates. I'm not sure what a duplicate IP would have to do with this problem since the serviio server listens on the localhost (127.0.0.1) IP.

In the meantime the Linux server developed the issue whereby one of the 8 cores goes into 100% usage mode and cycles that 100% usage between all of the 8 cores. That is usually caused by the Opera browser. Wasn't it this time. Neither was it either of the two Vivaldi browsers I had up. I closed all programs I had running and the issue was still there. That left the other process that could do it and that was MATE/caja (the desktop). Logging out and back normally fixed it. Not this time around. Well, reboot needed. Even that hung. I had to push the reset button.

After getting everything back up, I returned to this problem. Well, now I no longer get the address issue. Instead I now get:

Great. Maybe a 2.1 issue. So I retried 2.0. It gives me the duplicate address issue. What duplicate address? The program needs to put into the log what the duplicate address is.

As for the null issue with 2.1... here is its log:

Sigh

Bummer. The null error is a problem with the database. I don't know if any way to resolve that except delete Serviio and install fresh. But my Linux experience is limited and mostly out of date. If Zip notices this post, perhaps he can suggest something. I do see further down the log that it suggests the possibility of something already having the DB open. The way Derby is implemented in Serviio is as a single instance function. If something was already using the DB, Serviio can't open it. Perhaps another instance of Serviio was running, but that's just a guess.

I am at a loss over the duplicate address issue. Serviio doesn't just listen to localhost, it also binds to the active NIC in the computer. That's why I asked if you have more than one, because multiple NICs can confuse the auto bind function and you have to manually set it. However, to do that Serviio has to be running, because it's done in the console. Like I said, I'm comfused...

The instructions for updating to a newer version is to remove all files, except for two of them. In my case, I installed 2.1, renamed the existing serviio to serviio2.0 and renamed the 2.1 to serviio. I then deleted the two files and copied them over from the 2.0 install. Impossible to have something already using the DB as the computer was just rebooted.

Didn't know about the binding to the NIC. Only one in this box, the one built into the mobo.

I'll reinstall 2.1 and not rename it. The loss of the DB is not a great loss as the configuration as to where to get the files is extremely simple.

Update: Starting from scratch, 2.1 now starts. No idea why it did not like the two DB files: library and plugins.

I had another issue with 2.0, which 2.1 seems to have fixed and that is finding .dsf audio files and adding them to the database. 2.0 would just not do it.

I'm testing out .dsf playback and only have 18 files. I just set up a system for ripping my SACDs. I put in a new (old model) AVR that will play .dsf over DLNA. We'll see how that goes in a wee bit.