Interface Host based report throws the message "An error occurred! Control 30002" and causes the nfa_mysqlCSE service to stop on the Linux Harvester server.
Article ID: 4430
Updated On:
Products
Issue/Introduction
Interface Host based report throws the message "Error - an error occurred control 30002" and causes the nfa_mysqlCSE service to stop on the Linux Harvester server.
<Please see attached file for image>
The /opt/CA/NFA/data/<servername>.err file shows an error like below:
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2016-10-18 20:57:57 6413 [Note] Plugin 'FEDERATED' is disabled.
2016-10-18 20:57:57 6413 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-10-18 20:57:57 6413 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-18 20:57:57 6413 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-18 20:57:57 6413 [Note] InnoDB: Memory barrier is not used
2016-10-18 20:57:57 6413 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-10-18 20:57:57 6413 [Note] InnoDB: Using CPU crc32 instructions
2016-10-18 20:57:57 6413 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-10-18 20:57:57 6413 [Note] InnoDB: Completed initialization of buffer pool
2016-10-18 20:57:57 6413 [Note] InnoDB: Highest supported file format is Barracuda.
2016-10-18 20:57:57 6413 [Note] InnoDB: The log sequence numbers 1600667 and 1600667 in ibdata files do not match the log sequence number 1600847 in the ib_logfiles!
2016-10-18 20:57:57 6413 [Note] InnoDB: Database was not shutdown normally!
2016-10-18 20:57:57 6413 [Note] InnoDB: Starting crash recovery.
2016-10-18 20:57:57 6413 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-10-18 20:57:57 6413 [Note] InnoDB: Restoring possible half-written data pages
2016-10-18 20:57:57 6413 [Note] InnoDB: from the doublewrite buffer...
2016-10-18 20:57:57 6413 [Note] InnoDB: 128 rollback segment(s) are active.
2016-10-18 20:57:57 6413 [Note] InnoDB: Waiting for purge to start
2016-10-18 20:57:57 6413 [Note] InnoDB: 5.6.22 started; log sequence number 1600847
2016-10-18 20:57:57 6413 [Note] Server hostname (bind-address): '*'; port: 3307
2016-10-18 20:57:57 6413 [Note] IPv6 is available.
2016-10-18 20:57:57 6413 [Note] - '::' resolves to '::';
2016-10-18 20:57:57 6413 [Note] Server socket created on IP: '::'.
2016-10-18 20:57:57 6413 [Note] Event Scheduler: Loaded 0 events
2016-10-18 20:57:57 6413 [Note] /opt/CA/NFA/Netflow/bin/mysqld: ready for connections.
Version: '5.6.22' socket: '/opt/CA/NFA/Netflow/data/mysql.sock' port: 3307 Source distribution
2016-10-18 20:58:08 6413 [Warning] IP address 'xxx.xxx.xxx.xxx' could not be resolved: Name or service not known
2016-10-18 20:58:08 6413 [Warning] IP address 'xxx.xxx.xxx.xxx' could not be resolved: Name or service not known
2016-10-18 21:50:32 11785 [Note] /opt/CA/NFA/Netflow/bin/mysqld: ready for connections.
Version: '5.6.22' socket: '/opt/CA/NFA/Netflow/data/mysql.sock' port: 3307 Source distribution
RPR CSE data dir is [/opt/CA/NFA/Netflow//datafiles/ReaperArchive]
RPR CSE log file is [/opt/CA/NFA/Netflow//Logs/RPRStorageEngine.log]
RPR CSE ready to load dynlib [/opt/CA/NFA/Netflow//bin/libRPRStorageEngine.so]
RPR CSE data dir is [/opt/CA/NFA/Netflow//datafiles/ReaperArchive]
RPR CSE log file is [/opt/CA/NFA/Netflow//Logs/RPRStorageEngine.log]
RPR CSE ready to load dynlib [/opt/CA/NFA/Netflow//bin/libRPRStorageEngine.so]
01:50:51 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=268435456
read_buffer_size=16777216
max_used_connections=6
max_threads=250
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6409563 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1ec1080
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7fafd2df3e28 thread_stack 0x40000
/opt/CA/NFA/Netflow/bin/mysqld(my_print_stacktrace+0x35)[0x90edf5]
/opt/CA/NFA/Netflow/bin/mysqld(handle_fatal_signal+0x37b)[0x64ed0b]
/lib64/libpthread.so.0[0x3d8e60f790]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fafa40013e0): RPR CSE data dir is [/opt/CA/NFA/Netflow//datafiles/ReaperArchive]
Environment
Resolution
1. Connect to an SSH session with the RedHat Harvester.
2. Change directory to:
cd /opt/CA/NFA/Netflow/Logs
3. Create the log file /opt/CA/NFA/Netflow/Logs/NFAStorageEngine.log
vi NFAStorageEngine.log
4. Grant permissions to the file.
chmod 777 NFAStorageEngine.log
5. Restart the nfa_mysqlCSE service on the Harvester.
service nfa_mysqlCSE restart
6. Open a new interface report and drill down to a specific Protocol and then a Host and ensure that you no longer see the error.
7. If an error persists review the new log file /opt/CA/NFA/Netflow/Logs/NFAStorageEngine.log for details.
Attachments
Feedback
