Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle
Hi Jérôme If you've never modified the default Java memory settings, for Taskomatic, or Tomcat memory settings it's possibly running out of memory and task is crashing. This is a known issue, particularly when you sync large repos etc. See following link for more info: https://docs.oracle.com/cd/E92593_01/E90695/html/swk24-issues-memory.html You can see what Taskomatic is currently using by checking status: # systemctl status taskomatic.service ● taskomatic.service - Taskomatic Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-02-20 14:18:56 GMT; 1 day 23h ago Process: 46068 ExecStop=/usr/sbin/taskomatic stop (code=exited, status=0/SUCCESS) Process: 49351 ExecStart=/usr/sbin/taskomatic start (code=exited, status=0/SUCCESS) Main PID: 49377 (taskomaticd) CGroup: /system.slice/taskomatic.service ├─49377 /usr/bin/taskomaticd /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf wrapper.pidfile=/var/run//taskomatic.pid wrapper.daemonize=TRUE └─49383 /usr/bin/java -Dibm.dst.compatibility=true -Dfile.encoding=UTF-8 -Xms256m -Xmx1024m -Djava.library.path=/usr/lib:/usr/lib64:/usr/lib/oracle/11.2/client64/lib:/usr/lib/oracle/11.2/client/lib -classpath /usr/share/jav... Feb 20 14:18:56 systemd[1]: Starting Taskomatic... Feb 20 14:18:56 taskomatic[49351]: Starting RHN Taskomatic... Feb 20 14:18:56 wrapper[49377]: --> Wrapper Started as Daemon Feb 20 14:18:56 wrapper[49377]: Launching a JVM... Feb 20 14:18:56 systemd[1]: Started Taskomatic. # After changing the memory size you'll need to re-start Taskomatic. Regards Phil -Original Message- From: spacewalk-list-boun...@redhat.com On Behalf Of jerome.me...@lcsystems.ch Sent: 20 February 2019 10:20 To: 'Robert Paschedag' ; spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle Hi Robert, Thanks for your quick reply. It is good to know that isn't a application's issue ;) Do you know if there's a possibility to tune the DB to avoid this problem? Actually I've the SW 2.8 Best regards, Jérôme -Original Message- From: Robert Paschedag [mailto:robert.pasche...@web.de] Sent: Dienstag, 19. Februar 2019 18:31 To: spacewalk-list@redhat.com; Jérôme Meyer; 'spacewalk-list@redhat.com' Subject: Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle Am 19. Februar 2019 16:44:24 MEZ schrieb "Jérôme Meyer" : >Hi Everyone, > >I'm using the spacewalk-manage-channel-lifecycle to manage my >spacewalk's channel. > >Sometimes when I run this command, I've received this following error >on epel channel but not on any other channel. >At the end I've runned with channel exclusion (-x >dev-epel7-centos7-x86_64) and all was fine but it isn't the solution... > > >1) In this case I just started the command a second time. This is the >reason why there is no package. > >2) The only difference I see between the epel channel and the others >is that there are a lot of packets to transfert. > > ># spacewalk-manage-channel-lifecycle -c dev-centos7-x86_64 --promote >INFO: Merging packages from dev-centos7-x86_64 into test-centos7-x86_64 >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64 >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-centosplus into >test-centos7-x86_64-centosplus >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-centosplus >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-extras into >test-centos7-x86_64-extras >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-extras >INFO: Added 0 errata > >[...] > >INFO: Merging packages from dev-epel7-centos7-x86_64 into >test-epel7-centos7-x86_64 >Traceback (most recent call last): > File "/bin/spacewalk-manage-channel-lifecycle", line 575, in >merge_channels(child_source, child_dest) File >"/bin/spacewalk-manage-channel-lifecycle", line 213, in merge_channels >dest_label) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ >return self.__send(self.__name, args) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request >verbose=self.__verbose > File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request >return self.single_request(host, handler, request_body, verbose) >File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request >response.msg, >xmlrpclib.ProtocolError: chlxintmgmtp01.weforum.local/rpc/api: 500 Internal Server Error> What I could think of, is that there ar
Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle
Hi Robert, Thanks for your quick reply. It is good to know that isn't a application's issue ;) Do you know if there's a possibility to tune the DB to avoid this problem? Actually I've the SW 2.8 Best regards, Jérôme -Original Message- From: Robert Paschedag [mailto:robert.pasche...@web.de] Sent: Dienstag, 19. Februar 2019 18:31 To: spacewalk-list@redhat.com; Jérôme Meyer; 'spacewalk-list@redhat.com' Subject: Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle Am 19. Februar 2019 16:44:24 MEZ schrieb "Jérôme Meyer" : >Hi Everyone, > >I'm using the spacewalk-manage-channel-lifecycle to manage my >spacewalk's channel. > >Sometimes when I run this command, I've received this following error >on epel channel but not on any other channel. >At the end I've runned with channel exclusion (-x >dev-epel7-centos7-x86_64) and all was fine but it isn't the solution... > > >1) In this case I just started the command a second time. This is the >reason why there is no package. > >2) The only difference I see between the epel channel and the others >is that there are a lot of packets to transfert. > > ># spacewalk-manage-channel-lifecycle -c dev-centos7-x86_64 --promote >INFO: Merging packages from dev-centos7-x86_64 into test-centos7-x86_64 >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64 >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-centosplus into >test-centos7-x86_64-centosplus >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-centosplus >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-extras into >test-centos7-x86_64-extras >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-extras >INFO: Added 0 errata > >[...] > >INFO: Merging packages from dev-epel7-centos7-x86_64 into >test-epel7-centos7-x86_64 >Traceback (most recent call last): > File "/bin/spacewalk-manage-channel-lifecycle", line 575, in >merge_channels(child_source, child_dest) File >"/bin/spacewalk-manage-channel-lifecycle", line 213, in merge_channels >dest_label) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ >return self.__send(self.__name, args) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request >verbose=self.__verbose > File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request >return self.single_request(host, handler, request_body, verbose) >File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request >response.msg, >xmlrpclib.ProtocolError: chlxintmgmtp01.weforum.local/rpc/api: 500 Internal Server Error> What I could think of, is that there are too many transaction going onto the database and it just takes too long so you get that 500 error. Had this when I was to clean (and archive) finished actions. Had to do this in steps Otherwise I got an 500 error. But that was somewhere in SW 2.7 I think. Robert > > >Has anyone ever had this problem before? >A suggestion or an idea that could help me? > >Thanks and best regards, >Jérôme -- sent from my mobile device smime.p7s Description: S/MIME cryptographic signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle
Am 19. Februar 2019 16:44:24 MEZ schrieb "Jérôme Meyer" : >Hi Everyone, > >I'm using the spacewalk-manage-channel-lifecycle to manage my >spacewalk's channel. > >Sometimes when I run this command, I've received this following error >on epel channel but not on any other channel. >At the end I've runned with channel exclusion (-x >dev-epel7-centos7-x86_64) and all was fine but it isn't the solution... > > >1) In this case I just started the command a second time. This is the >reason why there is no package. > >2) The only difference I see between the epel channel and the others >is that there are a lot of packets to transfert. > > ># spacewalk-manage-channel-lifecycle -c dev-centos7-x86_64 --promote >INFO: Merging packages from dev-centos7-x86_64 into test-centos7-x86_64 >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64 >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-centosplus into >test-centos7-x86_64-centosplus >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-centosplus >INFO: Added 0 errata > >INFO: Merging packages from dev-centos7-x86_64-extras into >test-centos7-x86_64-extras >INFO: Added 0 packages >INFO: Merging errata into test-centos7-x86_64-extras >INFO: Added 0 errata > >[...] > >INFO: Merging packages from dev-epel7-centos7-x86_64 into >test-epel7-centos7-x86_64 >Traceback (most recent call last): > File "/bin/spacewalk-manage-channel-lifecycle", line 575, in >merge_channels(child_source, child_dest) >File "/bin/spacewalk-manage-channel-lifecycle", line 213, in >merge_channels >dest_label) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ >return self.__send(self.__name, args) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request >verbose=self.__verbose > File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request >return self.single_request(host, handler, request_body, verbose) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request >response.msg, >xmlrpclib.ProtocolError: chlxintmgmtp01.weforum.local/rpc/api: 500 Internal Server Error> What I could think of, is that there are too many transaction going onto the database and it just takes too long so you get that 500 error. Had this when I was to clean (and archive) finished actions. Had to do this in steps Otherwise I got an 500 error. But that was somewhere in SW 2.7 I think. Robert > > >Has anyone ever had this problem before? >A suggestion or an idea that could help me? > >Thanks and best regards, >Jérôme -- sent from my mobile device ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] xmlrpclib.ProtocolError issue with spacewalk-manage-channel-lifecycle
Hi Everyone, I'm using the spacewalk-manage-channel-lifecycle to manage my spacewalk's channel. Sometimes when I run this command, I've received this following error on epel channel but not on any other channel. At the end I've runned with channel exclusion (-x dev-epel7-centos7-x86_64) and all was fine but it isn't the solution... 1) In this case I just started the command a second time. This is the reason why there is no package. 2) The only difference I see between the epel channel and the others is that there are a lot of packets to transfert. # spacewalk-manage-channel-lifecycle -c dev-centos7-x86_64 --promote INFO: Merging packages from dev-centos7-x86_64 into test-centos7-x86_64 INFO: Added 0 packages INFO: Merging errata into test-centos7-x86_64 INFO: Added 0 errata INFO: Merging packages from dev-centos7-x86_64-centosplus into test-centos7-x86_64-centosplus INFO: Added 0 packages INFO: Merging errata into test-centos7-x86_64-centosplus INFO: Added 0 errata INFO: Merging packages from dev-centos7-x86_64-extras into test-centos7-x86_64-extras INFO: Added 0 packages INFO: Merging errata into test-centos7-x86_64-extras INFO: Added 0 errata [...] INFO: Merging packages from dev-epel7-centos7-x86_64 into test-epel7-centos7-x86_64 Traceback (most recent call last): File "/bin/spacewalk-manage-channel-lifecycle", line 575, in merge_channels(child_source, child_dest) File "/bin/spacewalk-manage-channel-lifecycle", line 213, in merge_channels dest_label) File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1273, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1321, in single_request response.msg, xmlrpclib.ProtocolError: Has anyone ever had this problem before? A suggestion or an idea that could help me? Thanks and best regards, Jérôme smime.p7s Description: S/MIME cryptographic signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
