I was wondering if anyone has seen this issue before. I have install an OS Deployment server to 3 of my relays so we can do imaging. We have 3 facilities that are all using this method, 1 out of 3 relay are not behaving. So what’s occurring is that, port 4011 would listed :4011 when ran netstat -a after OS deployment server installed. This port would randomly close in X amount of hours some time after 1 day. Restarting Bigfix bare metal server service will not recover port 4011. The only thing to get port 4011 back online I have to send a full server sync from the server management in console. The other 2 servers just running find without any issue. I have ran netstat -aon | findstr 4011 to see what is using, and nothing return. Could server hardware be part of this failure? or something? all 3 servers are having the same spec as well.
Hello,
I don’t think that the full sync could be involved because basically, apart from restarting the bare metal service twice (at the beginning and at the end) it synchronizes the deployment objects (profiles, images, drivers) that are not involved in the service on the port 4011.
Did you try to wait some time and restart the service again? Maybe something is blocking the port and it’s released after a while.
Sergio
Thank you! that’s interesting when I did full sync port 4011 recover. Yes I did wait and restart the service again but doesn’t help. We did check our enterprise AV and they were not blocked. Can’t seem to figured out blocking it. I went as far as rebuilt the server as well and still same result.
“The port is not open” is probably a symptom, rather than a cause.
If the port is not open, the most likely thing is that the service isn’t running. Check the Windows Event Logs, as well as the Bare Metal Server logs (at C:\BFOSD Files\logs by default, especially vm.log but the others as well if you don’t see issues there).
If the service does appear to be running, then you can look at ‘why is the port closed if the service is running’.
Please check those and then report back here, or open a Support Ticket if you would like some hands-on help troubleshooting and reviewing the logs.
The only thing I found from BFOSD logs is this error below. It recording it through out the day yesterday in the vm.log. I have check other logs from BFOSD logs nothing stand out or mention services is not running.
[2025/02/10 10:30:19:840] VM Error: Input/output error [NEF:1876]
[2025/02/10 10:30:19:840] The error was raised by utils.rbc, in CloseFileOnError, line 2899
Windows event viewer does report issue with Rembo service, but it appear in the same time when I did full sync. The first task/component in the full sync does have script to delete rembo service/registry and rebuild it. So I am wondering that’s why it reporting in the event viewer. I’ll check the event view the next time it stop.
The description for Event ID 0 from source Rembo Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
So you’re getting repeated instances of that VM Error in the vm.log? I haven’t seen that message but it does look like it’s worth some focus.
I’d check for the next instance of you noticing the service is not working / port is closed, and see whether you can correlate the process stopping to this error message (or to any other message).