Job failing with error unable to rename repcmd.log

[Raviraj]

We are triggering replicate by using scheduling tool and periodically checking the status if replicate completed or not. Although the replicate load is going success the job is failing with the error Failed to rename file repcmd.log to repcmd__240417043324.log .

[Dana_Baldwin]

Hi @Raviraj 

Is Replicate hosted on Windows or Linux?

Does the account the service runs as have permissions to the ../data/logs directory?

Dana

[Heinvandenheuvel]

>>  failing with the error Failed to rename file repcmd.log to repcmd__240417043324.log

This action is taking as  first step, before the actual task activities.

Did it ever work? If not, then it is 99.99% sure a permissions issue are per Dana.

Sudo to the repctl user and try a rename interactively?

Did it work for a long time? Maybe something 'filled up'? May we assume you schedule a shell script to launch REPCTL to EXECUTE the task? I recommend augmenting that with quickly reading all repcmd__*.log file.

• If they look as expected just remove them or ZIP -m into a 'good logs' container.
• If they look suspect, move them to a 'review' folder or zip file and perhaps even send in an Email.

Hein.

[john_wang]

Hello @Raviraj ,

Besides @Dana_Baldwin and @Heinvandenheuvel , We've encountered similar issues with other customers, often stemming from third-party monitoring and security software running on the Replicate server. These programs continuously monitor and scan (new) files operations, which can occasionally result in locking or delays, leading to the errors experienced by Replicate. We hope this explanation sheds some light on the situation.

John.

[Raviraj]

Thanks Dana for the reply. As per my understanding replicate service writes and renames the repcmd files, is it not the case ? 

[Raviraj]

By the way its running in windows

[Raviraj]

thanks John for the reply. Could you please confirm how that was fixed? anyway to fix which process is causing the lock?

[Raviraj]

Hi Hein

The account was able to start the replicate job, its monitoring the status of the job and failing after sometime without getting the run status and with this error

Thanks 

Raviraj

[john_wang]

Hello @Raviraj ,

Thank you for the update. To address the issue, we can explore several troubleshooting options:

1. Check the Windows Event Viewer: This can provide additional insights into the issue.

2. Verify for File Locks: Determine if any program or process has locked the file during the occurrence of the error.

3. Review Scheduled Tasks: Examine the schedulers to identify if too many tasks are set to start/stop in the exact same time. If so, consider spacing them out by several seconds to mitigate potential conflicts.

Looks to me the (3) probably is the root cause, as whenever a schedule initiate the task, file "repcmd.log" will be renamed. (Please take notes it's not the task log file but is "repcmd" file).

Hope this helps.

John.

[Heinvandenheuvel]

3>> Examine the schedulers to identify if too many tasks are set to start/stop in the exact same time

Yes, that's the most likely cause.

@Raviraj check the creation time for the repcmd.*log files around 2024 04 17 04 33 24

Are there multiple files in the same second?

Hein.