Error In Setting Gid To 0
Contents |
.identity; uid; gid; 2410; 1122514 Technote (troubleshooting) Problem(Abstract) This technote explains why the error, ./identity/uid is not set-id, will
Logrotate Operation Not Permitted
occur when attempting to work in a VOB or set to a error creating output file /var/lib/logrotate/status.tmp: permission denied view using IBM Rational ClearCase. Symptom Attempts to access a VOB, such as cat a file, or
Logrotate Error Creating Unique Temp File: Permission Denied
set to a view, results in the following error: ./identity/uid is not set-id The vob_log contains an error like: Error: ./identity/uid is not set-id". Note: This error will also error error creating unique temp file permission denied logrotate be found in the view_log and the albd_log if a setview command fails. Cause The permissions on the VOB's or view's .identity directory files are incorrect. Diagnosing the problem Change directory (cd) to the VOB or view's storage area's .identity subdirectory and execute the following command. ls -la -r----x--- 1 vobadm vobadm 0 Jun 8 08:50 gid -r----x--- 1 logrotate error opening permission denied vobadm users 0 Jun 8 08:50 group.1 -r----s--- 1 vobadm other 0 Jun 8 08:50 group.2 -r----x--- 1 vobadm vobadm 0 Jun 8 08:50 uid Note the sticky bit is missing on, gid, group.1 and uid. Resolving the problem For VOBs: Change directory (cd) to the VOB or view's storage area's .identity subdirectory and execute the following commands: cd /net/hostname/vobstore/testvob.vbs/.identity chmod 4400 uid chmod 2410 gid chmod 2410 group.xxx (where xxx is an integer) umount and mountthe VOB for the permissions change to take effect: cleartool umount /vobs/testvob For views: Change directory to the view storage area's .identity subdirectory and execute: cd /net/hostname/viewstore/view/.identity chmod 4400 uid chmod 2410 gid chmod 2410 group.xxx (where xxx is an integer) Then exit the view and kill and or restart the view_server for this view for the permissions change to take effect. Note: To find and kill the view server process: %>cleartool endview -server testview or %>ps -ef | grep view_server user 11009 8889 0 17:04:09 pts/3 0:00 view_server /viewstore/testview.vws -u.... %>kill -9 11009 Document informa
2 years ago error changing owner when run as user Reported by: david0 Owned by: tsmetana@… Priority: major Component: logrotate
Error: Error Creating State File /var/lib/logrotate/status: Permission Denied
Keywords: Cc: Blocked By: Blocking: Description Hi, I run logrotate create logrotate on an server to rotate logs that created by apache (which is not
Logrotate Failed To Rename Permission Denied
the user running logrotate). Both users have rw permissions through the group that is assigned to logfiles. It looks like logrotate tries http://www.ibm.com/support/docview.wss?uid=swg21122514 to algin the owner rights of all revisions when rotating... which is uneccessary in my case and will always fail. TL;DR: Would it be an option to either skip owner changing when geteuid()!=0 and geteuid()!=file_uid or to add an configuration option the prevent owner changes? Log: https://fedorahosted.org/logrotate/ticket/43 -rw-rw-r-- 1 www-data vagrant 5 Sep 6 07:55 test.log -rw-r--r-- 1 vagrant vagrant 6 Sep 6 07:55 test.log.1 reading config file test-config.24 Handling 1 logs rotating pattern: /home/vagrant/logrotate/test/test*.log forced from command line (1 rotations) empty log files are rotated, old logs are removed considering log /home/vagrant/logrotate/test/test.log log needs rotating rotating log /home/vagrant/logrotate/test/test.log, log->rotateCount is 1 dateext suffix '-20140906' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' renaming /home/vagrant/logrotate/test/test.log.1 to /home/vagrant/logrotate/test/test.log.2 (rotatecount 1, logstart 1, i 1), renaming /home/vagrant/logrotate/test/test.log.0 to /home/vagrant/logrotate/test/test.log.1 (rotatecount 1, logstart 1, i 0), old log /home/vagrant/logrotate/test/test.log.0 does not exist renaming /home/vagrant/logrotate/test/test.log to /home/vagrant/logrotate/test/test.log.1 creating new /home/vagrant/logrotate/test/test.log mode = 0664 uid = 33 gid = 900 error: error setting owner of /home/vagrant/logrotate/test/test.log to uid 33 and gid 900: Operation not permitted Change History comment:1 Changed 2 years ago by jkaluza What logrotate version is this? comment:2 Changed 2 y
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://superuser.com/questions/748999/winscp-set-gid-error about Stack Overflow the company Business Learn more about hiring developers or posting http://unix.stackexchange.com/questions/250100/logrotate-fails-to-rotate-logs-error-setting-owner ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise permission denied to the top WinSCP Set GID error up vote 0 down vote favorite I'm asking this question on behalf of a customer who called into my help desk. He was using WinSCP to try and change permissions of a directories and it's directories. He set RWX for both user and group (nothing for other), he checked the box to set GID so it's subdirectories would inherit the permissions, and he error creating unique checked the box to change the permissions of the directory and subdirectories recursively. After he pressed ok the permissions did not seem to change, although it works on other folders and he has been able to do this before. Any ideas on why this might be happening? linux permissions file-permissions winscp share|improve this question asked May 2 '14 at 16:36 UnworthyToast 1011 Is one of the folders/files below that particular folder owned by another user/group? Then he would not be allowed to change the permissions recursively. –mtak May 2 '14 at 17:47 I was thinking that, because I got that error when I tried to recreate it on one of my own folders, but he never received an error message. It's almost like the server he's connected to isn't receiving all the instructions. –UnworthyToast May 2 '14 at 17:50 If the customer is able to reproduce the problem, log file would be useful. Also what protocol is the customer using? –Martin Prikryl May 2 '14 at 19:43 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or l
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top logrotate fails to rotate logs: error setting owner up vote 1 down vote favorite Recently I've noticed that logrotate does not rotate my logs. user1@host:~$ /usr/sbin/logrotate /home/user1/logrotate.conf -v gives me an error: error: error setting owner of /home/logs/mylog.log.1 to uid 10111 and gid 10111: Operation not permitted error: error creating output file /var/lib/logrotate/status.tmp: Permission denied That gid confuses me, as user1 is only a member of a group with different gid: user1@host:~$ id uid=10111(user1) gid=1001(mygroup) groups=1001(mygroup) However, there's another group called user1, but, as I mentioned, actual user user1 is not its member: user1@host:~$ cat /etc/group | grep user1 user1:x:10111 It's something simple here, but I can't see it. UPDATE: here's what logrotate.conf looks like: /home/logs/*.log { rotate 7 daily copytruncate compress notifempty } logrotate 3.8.7 UPDATE 2: user1@host:~$ ls -la /home/logs/ -rw-r--r-- 1 user1 mygroup 1358383344 Dec 19 00:58 mylog.log ubuntu permissions users group logrotate share|improve this question edited Dec 19 '15 at 1:04 asked Dec 18 '15 at 2:39 hdf 5410 Can you add the corresponding stanza of your logrotate.conf? (Oh,and also your version of logrotate, just in case.) –Ulrich Schwarz Dec 18 '15 at 5:27 @UlrichSchwarz just updated the question, thanks. –hdf Dec 18 '15 at 5:36 1 Please add the output of ls -l /home/user1/*.log –wurtel Dec 18 '15 at 7:50 @wurtel nothing suspicious there, just updated. thanks. –hdf Dec 19 '15 at 1:05 Why is it trying to set group to 10111 if the log file itself is in group 1001(mygroup); that's what you need to find