Scheduler does not start after rebooting operating system, "libascurl.so.4: invalid ELF header" error is seen
Article ID: 421512
Updated On:
Products
Issue/Introduction
"libascurl.so.4: invalid ELF header" error is seen during scheduler startup after a reboot of the OS.
Cause
- AutoSys libraries somehow got corrupt
ls -al $AUTOSYS/lib/libascurl*
lrwxrwxrwx. 1 root root 59 Aug 27 10:00 libascurl.so -> /opt/CA/WorkloadAutomationAE/autosys/lib/libascurl.so.4.8.0
lrwxrwxrwx. 1 root root 59 Aug 27 10:00 libascurl.so.4 -> /opt/CA/WorkloadAutomationAE/autosys/lib/libascurl.so.4.8.0
-rwxr-xr-x. 1 root root 805938 May 30 01:20 libascurl.so.4.8.0
- Compare the file size above, it is the same on a good server (where autosys works fine) versus the bad server
- Next test was to check readelf on good server:
readelf -h libascurl.so.4.8.0
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: Advanced Micro Devices X86-64
Version: 0x1
Entry point address: 0x106e0
Start of program headers: 64 (bytes into file)
Start of section headers: 717784 (bytes into file)
Flags: 0x0
Size of this header: 64 (bytes)
Size of program headers: 56 (bytes)
Number of program headers: 7
Size of section headers: 64 (bytes)
Number of section headers: 31
Section header string table index: 28
- On the bad server, readelf errors out that it is in an invalid file
Resolution
- Stop any running AutoSys components on the bad server
- Copy the $AUTOSYS/lib folder (recursively) from a good server to bad server
- Start AutoSys
Feedback
