Summary of solutions for cwrsync server service startup failure

After testing, it turns out that the server did not stop cwrsync server when it was restarted automatically. If it is restarted suddenly, this error will be caused. If this problem occurs, we can delete the.pid file.

Trouble 1:

Event type: error
Event source: RsyncServer
Event type: no
Event ID: 0
Date: 2009-10-19
Event: 9:57:20
User: NT AUTHORITY\SYSTEM
Computer: SVCTAG-3SJMN2X
Description:
The description of the event ID (0) could not be found (in the resource (RsyncServer)). The local computer may not have the necessary registration information or message DLL files to display messages from the remote computer. You might use the /AUXSOURCE= identifier to retrieve the word description; See help and support for details. 下列信息是事件的一部分: RsyncServer: PID 5280: starting service `' failed: redirect_fd: open (1, C:\Program Files\ICW\rsyncd-stdin.log): 13 , Permission denied.

Log file permission problem!! Delete C:\Program Files\ICW\ rsyncd-stdin.log file!! cwrsync is created when it starts, and
is ready
Failure 2:

The RsyncServer service on the local computer started and stopped. Some services automatically stop if they have nothing to do, such as the "performance logging and alerts" service.

Boot it up, and a few seconds later it automatically shuts off

The solution is simple: delete the.pid file and start it again. After restarting the service, the file will be recreated.

Most errors that occur when the RsyncServer service on the local computer starts and then stops are caused by abnormal shutdown. This will not happen if it is a normal restart.