horizon错误汇集

Error during template rendering

In template /home/zengyl/workspace/horizon/openstack_dashboard/templates/_stylesheets.html, error at line3

Unable to apply CompilerFilter ('/home/zengyl/workspace/horizon/bin/less/lessc {infile} {outfile}'): [Errno 13] Permission denied

-----解决：chmod 770 /usr/bin/python

Permission denied: access to / denied

Cannot run program "/usr/bin/python2.7" (in directory "/

chmod -R o+x /usr/bin/

bash: /usr/bin/lesspipe: /bin/sh: bad interpreter: Permission denied

 chmod -R o+x /bin/sh

UPDATE: OK solved it, by setting chmod a+x on myroot directory. I don't like this at all though - surely it must be a security hole? What should I be doing instead?

[Mon Nov 05 09:27:50 2012] [error] [client 127.0.0.1] (13)Permission denied: mod_wsgi (pid=1515, process='', application='127.0.1.1|'): Call to fopen() failed for '/home/zengyl/workspace/horizon/openstack_dashboard/wsgi/django.wsgi'.

这个错误是访问路径的权限导致的，改成 chmod -R 755 /home/**/**/**即可

ubuntu下查看当前目录的大小

$ du -ch --max-depth=1

3.6M    ./deployers     
17G     ./log           
95M     ./deploy        
84M     ./tmp           
36K     ./work          
4.0K    ./lib           
436K    ./conf          
100K    ./data          
17G     .               
17G     总用量     

cpus一直在写日志文件，出现错误，ubuntu file/usr/lib/cups has insecure permissions

 chmod 555 /usr/lib/cups

rm -rf /tmp

 

ubuntu restart

 

按CTRL+ALT+F1回到commandline 界面，以用户ssh登陆
cat ~/.xsession-errors, 发现这一句
mkdtemp: private socket dir: Permission denied

google
#chmod 1777 /tmp

http://www.cnblogs.com/wuguderen/archive/2012/04/08/2437229.html

Incorrect password when trying to unlock screen

---

When trying to unlock the screen, such as after having locked it or just resumed the system from suspend or hibernate, it refuses to accept my password. If I switch to a tty screen, I can successfully login using exactly the same credentials, so I *know* it hasn't been ninjachanged.

If I pick Switch User, I get sent to the login screen. If I then login normally (with the same user and password), it unlocks and resumes my earlier session.

The only passwordy thing I know I've done is to set a root password, since FOR SOME REASON it demands it if I boot up into recovery mode and choose to start a root shell. Without one I know, I can't enter the shell.

CAUSE:
/sbin/unix_chkpwd has wrong group/permissions
SOLUTION:
sudo chown root:shadow /sbin/unix_chkpwd
sudo chmod 2755 /sbin/unix_chkpwd

According to a popular Linux Administration book, for security purposes, the permissions on the /etc/shadow file should be set to 600. If you set the permissions on /etc/shadow to 600 and use the Lock Screen function, on Ubuntu 9.04, you will not be able to unlock the screen. To log back in you will have to restart the computer. To re-enable the use of the Lock Screen function you'll need to set the permissions on /etc/shadow to 640.

i am in right permission and privilege of
"-rwxr-sr-x 1 root shadow 35432 2011-05-31 20:33 unix_chkpwd"
but i have not unlock the locked screen.

[Resolved]
sudo chown root:shadow /etc/gshadow
sudo chown root:shadow /etc/gshadow-
sudo chown root:shadow /etc/shadow
sudo chown root:shadow /etc/shadow-

from "root:root" to "root:shadow"

the issue will be resolved.

[Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']