Error message prompt:
Event Type: Information
Event Source: Rsyncserver
Event Type: None
Event id:0
Date: 2009-4-04
Event: 12:04:04
User:
Computer:
Describe:
The description of the event ID (0) (in resource (rsyncserver)) cannot be found. The local computer may not have the necessary registration information or a message DLL file to display messages from a remote computer. You may be able to use the/auxsource= identity to retrieve word descriptions, and to view Help and support for more information. The following information is part of the event: Rsyncserver:pid 2320: ' rsyncserver ' service stopped, exit Status:11.
Workaround:
Delete the. pid file or rename it, then start it again, this PID file will be generated again.
The cloud community gives the perfect solution: because it is a server, we can not every day on the server one of the checks, such a waste of time, and sometimes update the site or something.
So I think there is a good way, at least why can not start it, it is certainly the restart of the server before the problem may occur, then we can restart each time before the. pid file deleted, so that after normal startup Rsyncserver will also start normal. The best automated long-term approach for servers is to use batch processing with task scheduling, without any software being the best way to secure the server.
Task Schedule to add a batch
The code is as follows:
Copy Code code as follows:
@echo off
echo y | Del D:\program\cwRsyncServer\rsyncd.pid
REM Here you can write the server reboot code SHUTDOWN.EXE-R
PS: A point to write the full path, otherwise can not be deleted is not the directory, D:\program\cwRsyncServer for the program installation directory, you need to modify.
