#2241 Error pushing a merge
Closed: Duplicate 2 years ago Opened 2 years ago by mikem.

got the following

'''
[mike@localhost koji-tools]$ git push
Counting objects: 60, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (53/53), done.
Writing objects: 100% (60/60), 10.79 KiB | 0 bytes/s, done.
Total 60 (delta 28), reused 0 (delta 0)
remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_checkout_notify_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long)
remote: % self._get_c_name())
remote: /usr/lib64/python2.7/site-packages/cffi/model.py:526: UserWarning: 'git_merge_tree_flag_t' has no values explicitly defined; next version will refuse to guess which integer type it is meant to be (unsigned/signed, int/long)
remote: % self._get_c_name())
remote: Sending to redis to log activity
remote: Traceback (most recent call last):
remote: File "./hooks/post-receive.default", line 102, in <module>
remote: main(sys.argv[1:])
remote: File "./hooks/post-receive.default", line 98, in main
remote: run_as_post_receive_hook()
remote: File "./hooks/post-receive.default", line 82, in run_as_post_receive_hook
remote: 'commits': commits,
remote: File "/usr/lib/python2.7/site-packages/redis/client.py", line 1888, in publish
remote: return self.execute_command('PUBLISH', channel, message)
remote: File "/usr/lib/python2.7/site-packages/redis/client.py", line 565, in execute_command
remote: return self.parse_response(connection, command_name, **options)
remote: File "/usr/lib/python2.7/site-packages/redis/client.py", line 577, in parse_response
remote: response = connection.read_response()
remote: File "/usr/lib/python2.7/site-packages/redis/connection.py", line 574, in read_response
remote: raise response
remote: redis.exceptions.ResponseError: max number of clients reached
remote: Hook ./hooks/post-receive.default failed with error code 1
To ssh://git@pagure.io/koji-tools.git
727422b..853a5da master -> master
'''

Looks like the push succeeded, but the error is concerning


Closing as duplicate since I have started to reply to #2242 (even if this one was first)

Thanks for the report :)

Metadata Update from @pingou:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata