Fatal error: catreq.c:383 Invalid Catalog request

Fatal error: catreq.c:383 Invalid Catalog request


Fatal error: catreq.c:383 Invalid Catalog request

This error indicates an outdates director or SD in your environment. The best practice is to keep all FDs and SDs updated with the latest client versions. The FD and SD clients can be updated directly from your end user account. Just check the server tab or the storage tab, any device that needs to be updated will have an additional icon of a circle with an arrow pointing down in it.

If you have a DCE environment please also be sure to check if your Director or Web gui server needs to be updated via your admin user account. To do this check under the Director tab and it will show you if either the Director or Web Gui server needs to be updated.

    • Related Articles

    • Fatal error: catreq.c:383 Invalid Catalog request

      Fatal error: catreq.c:383 Invalid Catalog request This error indicates an outdates director or SD in your environment. The best practice is to keep all FDs and SDs updated with the latest client versions. The FD and SD clients can be updated directly ...

    • Error: ERR=No route to host

      Related: Fatal error: bsock.c:136 Unable to connect to Client: FD name Fatal error: No Job status returned from FD Problem: The Catalog server cannot connect to the FD IP/port and/or job was interrupted Common Solution: Please make sure ClusterLogics ...

    • Fatal error: Network error with FD during Backup

      Related Errors: ERR=Connection reset by peer Fatal error: No Job status returned from FD. Problem: It is likely the server was restarted and/or the ClusterLogics service interrupted Solution: Check firewall, restart service (Linux: service baroes-fd ...

    • Fatal error: CreateSGenerate VSS snapshots failed

      When getting VSS Volume Shadow Copy Service error , it's usually due to NTFS drive not having enough space , VSS core services alone requires at least 500 mb for each volume to be shadow copied , Try to check the event viewer and look for VSS logs , ...

    • Backup Job Failure - ERR=ERROR: index row size exceeds maximum 2712 for index "path_name_idx

      Hello, if you receive a backup error similar to the below Fatal error: sql_create.c:831 Fill Path table Query failed: INSERT INTO Path (Path) SELECT a.Path FROM (SELECT DISTINCT Path FROM batch) AS a WHERE NOT EXISTS (SELECT Path FROM Path WHERE Path ...