-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Installing Folscom Swift on Ubuntu 12.04 #34
Comments
Firstly, I did the same thing in my environment, it is OK. Then, I viewed the relevant code, it may be caused by the reason that the device /dev/log didn't exist. Could you confirm it? As to how to solve problem the device /dev/log didn't exist, it can be solved by installing rsyslog. |
@guanxiaohua2k6 Yes I can confirm /dev/log doesn't exist. However, syslog-ng is installed instead of rsyslog. Should i replace syslog-ng with rsyslog? |
It's OK to use syslog-ng instead of rsyslog. But you should change the /etc/syslog-ng.conf to make it use /dev/log. |
Here is what's already configured in /etc/syslog-ng/syslog-ng.conf. I believe dodai-deploy is already configuring syslog-ng. sysope@cn01040804:/dev$ cat /etc/syslog-ng/syslog-ng.conf source s_local { destination d_cons { file("/dev/console"); }; filter f_mesg { level(info..emerg) and not facility(mail,authpriv,cron); }; log { source(s_local); filter(f_mesg); destination(d_mesg); }; source s_dodai_instance_agent { file("/var/log/dodai/dodai-instance-agent.log"); }; filter f_hinemos_log { level(err..emerg); }; |
Could you confirm whether the service syslog-ng is started or not? |
syslog-ng wasn't started, so I tried to start it and got the following error: sysope@cn01040804:/dev$ sudo service syslog-ng status
|
If you are using NII academic cloud, the service syslog-ng should be started after the instance booted. Regarding the question, because it is related to the image created by NII, I think it's better to ask NII why the service syslog-ng couldn't started after the instance booted. |
@guanxiaohua2k6 I confirmed the issue was the syslog-ng conf and it was customized for 11.10 not 12.04, which uses syslog-ng 3.3, so syslog-ng was not starting correctly. I modified the config to use 3.3 syntax and was able to start syslog-ng service. I then was able to successfully install swift. Thanks again for your help. |
I see. Thank you for your reply. |
I get the following error when trying to install Folsom Swift:
info: Loading facts in /etc/puppet/modules/apt/lib/facter/apt_version.rb
info: Caching catalog for cn01040804.ecloud.nii.ac.jp
info: Applying configuration version '1353906220'
notice: /Stage[main]/Swift_f::Common/File[/etc/swift/cert.crt]/ensure: defined content as '{md5}80e307e35b94689794f6bdfdf2edcba9'
notice: /Stage[main]/Swift_f::Common/File[/etc/swift/cert.key]/ensure: defined content as '{md5}2647a92f16f9b6ec3b75dc4cb1dabe9a'
notice: /Stage[main]/Swift_f::Common/File[/etc/swift/swift.conf]/ensure: defined content as '{md5}92a37059ce0675c373c4292054d50b81'
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Package[swift]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Package[swift-proxy]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Swift_f::Swift_proxy::Install/File[/etc/swift/proxy-server.conf]/ensure: defined content as '{md5}bbe923b2e959d1e9907393e05c660276'
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Package[swauth]/ensure: ensure changed 'purged' to 'present'
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: No proxy-server running
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Device z1-136.187.33.85:6002/sdb1_"" with 100.0 weight got id 0
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Device z1-136.187.33.85:6001/sdb1_"" with 100.0 weight got id 0
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Device z1-136.187.33.85:6000/sdb1_"" with 100.0 weight got id 0
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Reassigned 262144 (100.00%) partitions. Balance is now 0.00.
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Reassigned 262144 (100.00%) partitions. Balance is now 0.00.
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Reassigned 262144 (100.00%) partitions. Balance is now 0.00.
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Starting proxy-server...(/etc/swift/proxy-server.conf)
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: Traceback (most recent call last):
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: File "/usr/bin/swift-proxy-server", line 22, in
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 126, in run_wsgi
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: log_to_console=kwargs.pop('verbose', False), log_route='wsgi')
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: File "/usr/lib/python2.7/dist-packages/swift/common/utils.py", line 608, in get_logger
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: raise e
notice: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: socket.error: [Errno 111] Connection refused
err: /Stage[main]/Swift_f::Swift_proxy::Install/Exec[/tmp/swift/proxy-init.sh sdb1 1 2>&1]/returns: change from notrun to 0 failed: /tmp/swift/proxy-init.sh sdb1 1 2>&1 returned 1 instead of one of [0] at /etc/puppet/modules/swift_f/manifests/swift_proxy/install.pp:29
notice: Finished catalog run in 26.57 seconds
Any support would be greatly appreciated.
The text was updated successfully, but these errors were encountered: