So when I reboot the PC that the server is installed on, the system status comes up on-air-services unknown
To get things to work I have to stop the service in the server manager and then restart, and then everything works fine.
Now if I reboot the PC again, I'm back to square one.
Here is the log after reboot:
2024-03-31 09:06:37, SDR Server Service 3.3 build 3236
2024-03-31 09:06:37, Path: C:\Program Files\SDR-Radio.com (V3)\SDRServerService.exe
2024-03-31 09:06:37, Compiled: Feb 5 2024, 07:34:44
-
2024-03-31 09:06:37, Data folder: C:\ProgramData\SDR-Radio.com\
2024-03-31 09:06:37, Product folder: C:\Windows\System32\config\systemprofile\AppData\Roaming\SDR-RADIO.com (V3)\
2024-03-31 09:06:37, Mapped logfile: 65,536 KB
-
2024-03-31 09:06:37, Open settings event Global\SDR-Server-V3-New-Settings, handle 00000000
2024-03-31 09:06:37, Create settings event Global\SDR-Server-V3-New-Settings, handle 00000288
2024-03-31 09:06:37, Reset settings event 1
-
-
2024-03-31 09:06:37, CServerService::OnStart
2024-03-31 09:06:37, CServerService::ServiceWorkerThread
2024-03-31 09:06:37, CoInitialize result = 00000000
2024-03-31 09:06:38, OnAir> Loading On-Air options
2024-03-31 09:06:38, OnAir> Loading On-Air options
2024-03-31 09:06:38, Listener> Loading GeoLite2 database
2024-03-31 09:06:40, Listener> -
2024-03-31 09:06:40, Listener> Network Address
2024-03-31 09:06:40, Listener> Result = 0
2024-03-31 09:06:40, Listener> Host = SDR
2024-03-31 09:06:40, Listener> Entry = 858D3F80
2024-03-31 09:06:40, Listener> Name = SDR
2024-03-31 09:06:40, Listener> Address 1 ..: 127.0.0.1
2024-03-31 09:06:40, Listener> -
2024-03-31 09:06:40, Listener> Firewall
2024-03-31 09:06:40, Listener> Enabled: Yes
2024-03-31 09:06:40, Listener> Blacklist entries: 0
2024-03-31 09:06:40, Listener> Whitelist entries: 0
2024-03-31 09:06:40, Listener> -
2024-03-31 09:06:40, Listener> Creating socket Overlapped
2024-03-31 09:06:40, Listener> Created socket 4560
2024-03-31 09:06:40, Listener> Enabling SO_REUSEADDR
2024-03-31 09:06:40, Listener> -
2024-03-31 09:06:40, Listener> Binding socket 4560 to 192.168.1.32:50101
2024-03-31 09:06:40, Listener> ***
2024-03-31 09:06:40, Listener> * Socket Bind failure: Cannot assign requested address.
2024-03-31 09:06:40, Listener> * Socket Bind failure: Check port 192.168.1.32:50101 is not in use by another program
2024-03-31 09:06:40, Listener> ***
2024-03-31 09:06:40, Security> Database = C:\ProgramData\SDR-Radio.com\SecurityDatabase_001.sqlite
2024-03-31 09:06:40, Security> Size = 20 KB
2024-03-31 09:06:40, Security> Opened C:\ProgramData\SDR-Radio.com\SecurityDatabase_001.sqlite
2024-03-31 09:06:40, Security> Table Security_901 Exists, 93 entries
2024-03-31 09:06:40, Security> -
-
Logfile
Address ......: 000000004B6E0000
Ready ........: 1
Updates ......: 46
SyncBits .....: 00000000
Used (chars) .: 2455
Size (chars) .: 33554432
Instance .....: 31-Mar-2024 09:06:37
Socket Bind failure
Re: Socket Bind failure
Are you starting the server twice during system startup?
{^_^}
{^_^}
Re: Socket Bind failure
My fix was to set the services to a delayed start, now that seems to fix things after the reboot
Re: Socket Bind failure
You might also explore setting a dependency on network being up. But, it works. Don't fix it unless you like exploring "why".
{^_-}
{^_-}