Hi ! I am a regular and satisfied user of Pulp 2.3 I am currently evaluating Pulp 2.4 and I am experiencing the same issue as described by Joseph. I install it on RHEL 6.4 (current 'authorized version for prod' here)
The major difference seem to be the introduction of Celery. I checked that my workers are running apache 1338 0.8 0.3 701460 24384 ? Sl 10:35 1:51 /usr/bin/python /usr/bin/celery beat --scheduler=pulp.server.async.scheduler.Scheduler --workdir=/var/lib/pulp/celery/ -f /var/log/pulp/celerybeat.log -l INFO --detach --pidfile=/var/run/pulp/celerybeat.pid apache 1394 0.5 0.5 621452 46152 ? Sl 10:35 1:14 /usr/bin/python -m celery.__main__ worker -c 1 -n [email protected] --events --app=pulp.server.async.app --loglevel=DEBUG --logfile=/var/log/pulp/reserved_resource_worker-0.log --pidfile=/var/run/pulp/reserved_resource_worker-0.pid apache 1476 0.5 0.5 621188 46140 ? Sl 10:35 1:14 /usr/bin/python -m celery.__main__ worker -c 1 -n [email protected] --events --app=pulp.server.async.app --loglevel=DEBUG --logfile=/var/log/pulp/reserved_resource_worker-1.log --pidfile=/var/run/pulp/reserved_resource_worker-1.pid apache 1505 0.0 0.4 392952 38480 ? S 10:35 0:00 /usr/bin/python -m celery.__main__ worker -c 1 -n [email protected] --events --app=pulp.server.async.app --loglevel=DEBUG --logfile=/var/log/pulp/reserved_resource_worker-0.log --pidfile=/var/run/pulp/reserved_resource_worker-0.pid apache 1548 0.0 0.4 392944 38472 ? S 10:35 0:00 /usr/bin/python -m celery.__main__ worker -c 1 -n [email protected] --events --app=pulp.server.async.app --loglevel=DEBUG --logfile=/var/log/pulp/reserved_resource_worker-1.log --pidfile=/var/run/pulp/reserved_resource_worker-1.pid stopping and startnig the pulp_workers looks ok $ sudo service pulp_workers stop celery init v10.0. Using config script: /etc/default/pulp_workers celery multi v3.1.11 (Cipater) > Stopping nodes... > [email protected]: TERM -> 6021 > [email protected]: TERM -> 6043 > Waiting for 2 nodes -> 6021, 6043...... > [email protected]: OK > Waiting for 1 node -> 6043.... > [email protected]: OK $ sudo service pulp_workers stop celery init v10.0. Using config script: /etc/default/pulp_workers celery multi v3.1.11 (Cipater) > [email protected]: DOWN > [email protected]: DOWN [osadmin@pulp-master ~]$ sudo service pulp_workers start celery init v10.0. Using config script: /etc/default/pulp_workers celery multi v3.1.11 (Cipater) > Starting nodes... > [email protected]: OK > [email protected]: OK And according to syslog (/var/log/messages) qpidd seems to see the workers registered Oct 23 14:32:42 pulp-master qpidd[1266]: 2014-10-23 14:32:42 [Store] notice Journal "[email protected]": Created Oct 23 14:32:43 pulp-master pulp: celery.worker.consumer:INFO: Connected to qpid://[email protected]:5672// Oct 23 14:32:43 pulp-master qpidd[1266]: 2014-10-23 14:32:43 [Store] notice Journal "[email protected]": Created Oct 23 14:32:44 pulp-master pulp: pulp.server.async.worker_watcher:INFO: New worker '[email protected]' discovered Oct 23 14:32:45 pulp-master pulp: pulp.server.async.worker_watcher:INFO: New worker '[email protected]' discovered pulp-admin login works $ pulp-admin login -u admin -p 'password' Successfully logged in. Session certificate will expire at Oct 30 12:40:43 2014 GMT. pulp-admin rpm repo list works pulp-admin rpm repo create works BUT pulp-admin rpm repo delete pulp-admin rpm repo update pulp-admin rpm repo sync run don't work. The commands are 'stuck' and if I interrupt them I get the following error stack trace: $ pulp-admin --debug rpm repo update --repo-id=myrepo --relative-url=myrepo/relative/url --feed=http://feed.url ^CTraceback (most recent call last): File "/usr/bin/pulp-admin", line 9, in <module> load_entry_point('pulp-client-admin==2.4.0', 'console_scripts', 'pulp-admin')() File "/usr/lib/python2.6/site-packages/pulp/client/admin/__init__.py", line 35, in main config_files, exception_handler_class=AdminExceptionHandler File "/usr/lib/python2.6/site-packages/pulp/client/launcher.py", line 109, in main code = cli.run(args) File "/usr/lib/python2.6/site-packages/pulp/client/extensions/core.py", line 478, in run exit_code = Cli.run(self, args) File "/usr/lib/python2.6/site-packages/okaara/cli.py", line 974, in run exit_code = command_or_section.execute(self.prompt, remaining_args) File "/usr/lib/python2.6/site-packages/pulp/client/extensions/extensions.py", line 224, in execute return self.method(*arg_list, **clean_kwargs) File "/usr/lib/python2.6/site-packages/pulp_rpm/extensions/admin/repo_create_update.py", line 271, in run importer_config, distributor_configs File "/usr/lib/python2.6/site-packages/pulp/bindings/repository.py", line 189, in update_repo_and_plugins return self.server.PUT(path, body) File "/usr/lib/python2.6/site-packages/pulp/bindings/server.py", line 102, in PUT return self._request('PUT', path, body=body, ensure_encoding=ensure_encoding) File "/usr/lib/python2.6/site-packages/pulp/bindings/server.py", line 143, in _request response_code, response_body = self.server_wrapper.request(method, url, body) File "/usr/lib/python2.6/site-packages/pulp/bindings/server.py", line 324, in request response = connection.getresponse() File "/usr/lib64/python2.6/httplib.py", line 990, in getresponse response.begin() File "/usr/lib64/python2.6/httplib.py", line 391, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.6/httplib.py", line 349, in _read_status line = self.fp.readline() File "/usr/lib64/python2.6/socket.py", line 433, in readline data = recv(1) File "/usr/lib64/python2.6/site-packages/M2Crypto/SSL/Connection.py", line 228, in read return self._read_bio(size) File "/usr/lib64/python2.6/site-packages/M2Crypto/SSL/Connection.py", line 213, in _read_bio return m2.ssl_read(self.ssl, size, self._timeout) KeyboardInterrupt I don't see errors in MongoDB logs and I am able to perform a show dbs with mongo I installed MongoDB from mongo repo http://downloads-distro.mongodb.org/repo/redhat/os/x86_64/ Do you have some recommendations on how to troubleshoot this issue ? Thanks Paul On Thu, Sep 25, 2014 at 9:24 PM, Randy Barlow <[email protected]> wrote: > On 09/25/2014 01:53 PM, Tata, Joseph wrote: >> But the server never responds, never times out and never actually >> performs the requested task. >> >> Any idea what's going on or how to correct this? > > Hi Joseph, > > Can you check your syslog to see if there are any error messages there? > Also, 2.4 is majorly different from 2.3 (it should have been called 3.0 > IMO.) Did you look at the release notes and follow all the instructions? > There are several new required processes in 2.4, and it might be that > they aren't all running. > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
