[IntelMQ-users] pipeline failed

Mon Apr 19 16:32:23 CEST 2021

Hi,

Looks like your local redis service died. To get more insight, we need
more logs. `journalctl -x -e -u redis-server.service` may help.

I again recommend you get some help from someone with linux system
administration or consultancy, that will make life much easier for you
and you can reach your goal faster.

Sebastian

On 4/19/21 9:56 AM, Soni, Drupad via IntelMQ-users wrote:
>
> Hi Sebastian/Bernhard,
>
>  
>
> After a while Intelmq worked smoothly now it is showing ES bot will
> start in 15 secs and pipeline is failed! Showing error below.
>
>  
>
> Pipeline failed.
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 484, in connect
>     sock = self._connect()
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 541, in _connect
>     raise err
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 529, in _connect
>     sock.connect(socket_address)
> ConnectionRefusedError: [Errno 111] Connection refused
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/redis/client.py", line 667, in execute_command
>     connection.send_command(*args)
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 610, in send_command
>     self.send_packed_command(self.pack_command(*args))
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 585, in send_packed_command
>     self.connect()
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 489, in connect
>     raise ConnectionError(self._error_message(e))
> redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 484, in connect
>     sock = self._connect()
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 541, in _connect
>     raise err
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 529, in _connect
>     sock.connect(socket_address)
> ConnectionRefusedError: [Errno 111] Connection refused
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/intelmq/lib/pipeline.py", line 258, in _receive
>     retval = self.pipe.lindex(self.internal_queue, -1)  # returns None if no value
>   File "/usr/lib/python3/dist-packages/redis/client.py", line 1311, in lindex
>     return self.execute_command('LINDEX', name, index)
>   File "/usr/lib/python3/dist-packages/redis/client.py", line 673, in execute_command
>     connection.send_command(*args)
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 610, in send_command
>     self.send_packed_command(self.pack_command(*args))
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 585, in send_packed_command
>     self.connect()
>   File "/usr/lib/python3/dist-packages/redis/connection.py", line 489, in connect
>     raise ConnectionError(self._error_message(e))
> redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/intelmq/lib/bot.py", line 272, in start
>     self.process()
>   File "/usr/lib/python3/dist-packages/intelmq/bots/outputs/elasticsearch/output.py", line 104, in process
>     event = self.receive_message()
>   File "/usr/lib/python3/dist-packages/intelmq/lib/bot.py", line 592, in receive_message
>     message = self.__source_pipeline.receive()
>   File "/usr/lib/python3/dist-packages/intelmq/lib/pipeline.py", line 124, in receive
>     retval = self._receive()
>   File "/usr/lib/python3/dist-packages/intelmq/lib/pipeline.py", line 267, in _receive
>     raise exceptions.PipelineError(exc)
> intelmq.lib.exceptions.PipelineError: pipeline failed - ConnectionError('Error 111 connecting to 127.0.0.1:6379. Connection refused.',)
>
>  
>
> Regards,
>
> Drupad Soni
>
> *KPMG – Cyber Security*
>
> Embassy Golf Links Business Park, Pebble Beach, 'B' Block,
>
> 1st & 2nd Floor, Off Intermediate Ring Road
>
> Mobile : +91 8140283894
>
> Know more about our *Cyber Security Services*
>
> https://home.kpmg.com/in/en/home/services/advisory/risk-consulting/it-advisory-services/cyber-security.html
>
>  
>
> ------------------------------------------------------------------------
> KPMG (in India) allows reasonable personal use of the e-mail system.
> Views and opinions expressed in these communications do not
> necessarily represent those of KPMG (in India).
>
> *******************************************************************************************************
> DISCLAIMER
> The information in this e-mail is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this
> e-mail by anyone else is unauthorized. If you have received this
> communication in error, please address with the subject heading
> "Received in error," send to postmaster1 at kpmg.com, then delete the
> e-mail and destroy any copies of it. If you are not the intended
> recipient, any disclosure, copying, distribution or any action taken
> or omitted to be taken in reliance on it, is prohibited and may be
> unlawful. Any opinions or advice contained in this e-mail are subject
> to the terms and conditions expressed in the governing KPMG client
> engagement letter. Opinions, conclusions and other information in this
> e-mail and any attachments that do not relate to the official business
> of the firm are neither given nor endorsed by it.
>
> KPMG cannot guarantee that e-mail communications are secure or
> error-free, as information could be intercepted, corrupted, amended,
> lost, destroyed, arrive late or incomplete, or contain viruses.
>
> KPMG, an Indian partnership and a member firm of KPMG International
> Cooperative ("KPMG International"), a Swiss entity that serves as a
> coordinating entity for a network of independent firms operating under
> the KPMG name. KPMG International Cooperative (“KPMG International”)
> provides no services to clients. Each member firm of KPMG
> International Cooperative (“KPMG International”) is a legally distinct
> and separate entity and each describes itself as such.
>
> “Notwithstanding anything inconsistent contained in the meeting invite
> to which this acceptance pertains, this acceptance is restricted
> solely to confirming my availability for the proposed call and should
> not be construed in any manner as acceptance of any other terms or
> conditions. Specifically, nothing contained herein may be construed as
> an acceptance (or deemed acceptance) of any request or notification
> for recording of the call, which can be done only if it is based on my
> explicit and written consent and subject to the terms and conditions
> on which such consent has been granted”
> *******************************************************************************************************
>
-- 
// Sebastian Wagner <wagner at cert.at> - T: +43 1 5056416 7201
// CERT Austria - https://www.cert.at/
// Eine Initiative der nic.at GmbH - https://www.nic.at/
// Firmenbuchnummer 172568b, LG Salzburg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cert.at/pipermail/intelmq-users/attachments/20210419/27c3b731/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.cert.at/pipermail/intelmq-users/attachments/20210419/27c3b731/attachment.sig>