/var/log permissions

I recently helped setup arch on a friends computer, I don't currently have arch installed myself so I have no way of checking this. I added his user to the log group so that he would be able to view logfiles without being root, if I remember correctly this worked great for me, the problem is there's only a few logs he can view.. Is this something that has changed recently or have the permissions accidentally been changed somehow..?
calle ~ $ ls -al /var/log/
total 1040
drwxr-xr-x 6 root root 4096 2009-07-13 23:38 .
drwxr-xr-x 13 root root 4096 2009-07-13 21:25 ..
drwxr-xr-x 2 root root 4096 2009-07-13 20:54 ConsoleKit
-rw-r--r-- 1 root users 15020 2009-07-13 22:21 Xorg.0.log
-rw-r--r-- 1 root users 15346 2009-07-13 21:07 Xorg.0.log.old
-rw-r----- 1 root root 16741 2009-07-14 14:33 auth.log
-rw------- 1 root root 1536 2009-07-14 13:56 btmp
-rw-r--r-- 1 root root 2536 2009-07-14 14:01 crond
-rw-r----- 1 root root 33353 2009-07-14 10:52 daemon.log
-rw-r--r-- 1 root root 26946 2009-07-13 22:20 dmesg.log
-rw-r----- 1 root root 3196 2009-07-14 13:57 errors.log
-rw-r----- 1 root root 261858 2009-07-14 14:26 everything.log
-rw------- 1 root root 24024 2009-07-13 22:21 faillog
drwxr-xr-x 2 root root 4096 2009-03-29 16:07 gdm
-rw-r----- 1 root root 225692 2009-07-14 07:07 kernel.log
drwxr-xr-x 2 root root 4096 2009-07-13 23:42 lastfm
-rw-r--r-- 1 root root 292292 2009-07-14 14:33 lastlog
-rw-r----- 1 root root 214065 2009-07-14 14:26 messages.log
drwxr-xr-x 2 root root 4096 2009-06-07 12:11 old
-rw-r--r-- 1 root root 36756 2009-07-14 01:01 pacman.log
-rw-r----- 1 root root 1067 2009-07-13 22:20 syslog.log
-rw-r----- 1 root root 454 2009-07-13 23:08 user.log
-rw-r--r-- 1 root root 97920 2009-07-14 14:33 wtmp
-rw-r--r-- 1 root root 583 2009-07-13 22:20 wvdial
calle ~ $
How is this supposed to work?? Could someone post the output of "ls -al /var/log"?
Thanks!

This was http://bugs.archlinux.org/task/15095 .  Should be fixed with the syslog-ng in [testing]

Similar Messages

  • [SOLVED] warning: directory permissions differ on var/log/wicd/

    Hi,
    I've seen several posts about this but I couldn't really figure out what's the appropriate action. Well, anyway I get the following error message when doing a pacman -Syu
    warning: directory permissions differ on var/log/wicd/
    filesystem: 1363 package: 755
    Is it a bug? Should I change the filepermission of the directory, and if so to what?
    Last edited by OMGitsUGOD (2009-09-18 10:38:32)

    This is sort of related,
    http://bbs.archlinux.org/viewtopic.php?pid=432588
    or at least thats the post at the end has the same file permisions as I have in /var/log/wicd.
    $ ls -la /var/log/ | grep wicd
    d-wxrw--wt 2 root root 4096 2009-08-27 07:58 wicd
    I'm pretty bad at this stuff, but isn't this rather 1361 than 1363, or am I totally wrong? And why not allow theowner to read the file?
    Last edited by OMGitsUGOD (2009-09-17 08:43:32)

  • GDM update: directory permissions differ on /var/log/gdm/

    Hello,
    Running Arch 64Bits kernel 3.9.9-1 with systemd and i got the following warning during a gdm update today:
    (1/6) upgrading libgdm [######################] 100%
    (2/6) upgrading gdm [######################] 100%
    warning: directory permissions differ on /var/log/gdm/
    filesystem: 711 package: 1770
    Why would gdm need some 1770 permissions for log files? Looks pretty suspicious to me, especially the sticky bit thing. What did i miss?
    PS: BTW the update is successful (it's a warning afterall, not an error)
    Thanks
    EDIT:
    Looks like the opposite situation than 3 years ago:
    https://bbs.archlinux.org/viewtopic.php?id=94681
    https://bugs.archlinux.org/task/19294
    EDIT2: here's what i have in /var/log:
    msytux666 var # ls -la
    total 64
    drwxr-xr-x 14 root root 4096 Jul 6 15:34 .
    drwxr-xr-x 20 root root 4096 Jul 16 20:24 ..
    -rwxrwxrwx 1 root root 4192 Jun 19 11:27 .com.zerog.registry.xml
    drwxr-xr-x 7 root root 4096 Jul 7 00:07 abs
    drwxr-xr-x 8 root root 4096 Jun 16 17:28 cache
    drwxr-xr-x 3 root root 4096 Jun 17 19:07 db
    drwxr-xr-x 2 root root 4096 May 31 20:40 empty
    drwxrwxr-x 2 root games 4096 May 31 20:40 games
    drwx--x--x 2 gdm gdm 4096 Jun 15 14:23 gdm
    drwxr-xr-x 26 root root 4096 Jul 16 01:13 lib
    drwxr-xr-x 2 root root 4096 May 31 20:40 local
    lrwxrwxrwx 1 root root 11 May 31 20:40 lock -> ../run/lock
    drwxr-xr-x 6 root root 4096 Jul 18 00:33 log
    lrwxrwxrwx 1 root root 10 May 31 20:40 mail -> spool/mail
    drwxr-xr-x 2 root root 4096 May 31 20:40 opt
    lrwxrwxrwx 1 root root 6 May 31 20:40 run -> ../run
    drwxr-xr-x 6 root root 4096 Jun 16 17:28 spool
    drwxrwxrwt 8 root root 4096 Jul 18 00:33 tmp
    gdm is owned by gdm, so why would it needs 1770 permissions?
    EDIT3:
    After further research i appear the way gdm is installed may matter.
    Well i installed gdm through pacman and always update it with pacman as well. Never manually compiled/make_install'd it nor used abs for it.
    Last edited by BGK (2013-07-19 21:37:13)

    Okay I'm confused ...
    Commit:https://projects.archlinux.org/svntogit … 92c38d536d
    @@ -68,8 +68,7 @@ package_gdm() {
    cd $pkgbase-$pkgver
    make DESTDIR="$pkgdir" install
    - chmod 1770 "$pkgdir/var/log/gdm"
    - chmod 700 "$pkgdir/var/lib/gdm/.config/dconf"
    + chmod 711 "$pkgdir/var/log/gdm"
    rm -r "$pkgdir/var/run" "$pkgdir/var/gdm"
    ### Split libgdm
    so that takes away the 1770 permissions, and replaces them with 711. 
    @@ -5,6 +5,7 @@ post_install() {
    getent passwd gdm > /dev/null 2>&1 || usr/sbin/useradd -c 'Gnome Display Manager' -u 120 -g gdm -d /var/lib/gdm -s /sbin/nologin gdm
    passwd -l gdm > /dev/null
    chown -R gdm:gdm /var/lib/gdm > /dev/null
    + chown root:gdm /var/log/gdm > /dev/null
    glib-compile-schemas /usr/share/glib-2.0/schemas
    gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor
    however:
    chown root:gdm /var/log/gdm > /dev/null
    .. is where I get confused.  This command makes root and the group gdm the new owners of /var/log/gdm, or did I go wrong somewhere?

  • Var/log/mail.log file empty

    My var/log/mail.log isn't logging anything, the file seems to empty since 4th March 2010 3:15 AM
    Have tried the below mentioned troubleshooting steps, but no luck though
    1. Stopped and restarted mail service
    2. Repaired disk permissions through disk utility application
    3. Repaired permissions through terminal diskutil
    4. Restarted daemons as suggested in this forum http://discussions.info.apple.com/thread.jspa?threadID=2088823&tstart=60
    5. Changed permissions as suggested on this forum http://forums.macosxhints.com/archive/index.php/t-13985.html
    Any help please!!!

    Change the archive log to 3 days. Make sure all three log levels are set to information. Restart mail and see if any thing appears in the logs.
    Also how are you viewing the logs - using SA or Console?
    Thanks,
    Henry

  • Private Secure Log Permissions being changed by someone????

    I have been having to repair the permissions on my ibook often. How do these get changed, by who, and what threat is it to me? How much control over my computer can one get????
    Below is the repair I just had to make.
    Repairing permissions for “Macintosh HD”
    Determining correct file permissions.
    Group differs on ./private/etc/authorization, should be 80, group is 0
    Owner and group corrected on ./private/etc/authorization
    Permissions corrected on ./private/etc/authorization
    Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
    Owner and group corrected on ./private/var/log/secure.log
    Permissions corrected on ./private/var/log/secure.log
    Permissions repair complete
    The privileges have been verified or repaired on the selected volume
      Mac OS X (10.4.9)  

    The permissions on the secure.log file are being changed by the weekly cron task, which is being run by Mac OS X itself as opposed to someone accessing the computer locally or over the network.
    (21837)

  • [SOLVED]Couldn't open file for 'Log debug file /var/log/tor/debug.log'

    Hello,
    I'm trying to run a tor relay on my arch linux box. Trying to launch the tor daemon, here's the log via
    $ systemctl status tor.service
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor v0.2.4.21 (git-505962724c05445f) running on Linux with Libevent 2.0.21-stable and OpenSSL 1.0.1g.
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Read configuration file "/etc/tor/torrc".
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening Socks listener on 127.0.0.1:9050
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening OR listener on 0.0.0.0:9798
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Couldn't open file for 'Log debug file /var/log/tor/debug.log': Permission denied
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed OR listener on 0.0.0.0:9798
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [err] Reading config failed--see warnings above.
    May 20 11:53:10 arch systemd[1]: tor.service: main process exited, code=exited, status=255/n/a
    May 20 11:53:10 arch systemd[1]: Unit tor.service entered failed state.
    Why the tor daemon cannot write into /var/log/tor/debug.log ?
    Here's my /etc/group
    root:x:0:root
    bin:x:1:root,bin,daemon
    daemon:x:2:root,bin,daemon
    sys:x:3:root,bin
    adm:x:4:root,daemon,nue
    tty:x:5:
    disk:x:6:root
    lp:x:7:daemon
    mem:x:8:
    kmem:x:9:
    wheel:x:10:root,nue
    ftp:x:11:
    mail:x:12:
    uucp:x:14:
    log:x:19:root
    utmp:x:20:
    locate:x:21:
    rfkill:x:24:
    smmsp:x:25:
    http:x:33:
    games:x:50:
    lock:x:54:
    uuidd:x:68:
    dbus:x:81:
    network:x:90:
    video:x:91:
    audio:x:92:
    optical:x:93:
    floppy:x:94:
    storage:x:95:
    scanner:x:96:
    power:x:98:
    nobody:x:99:
    users:x:100:
    systemd-journal:x:190:
    nue:x:1000:
    avahi:x:84:
    lxdm:x:121:
    polkitd:x:102:
    git:x:999:
    transmission:x:169:
    vboxusers:x:108:
    tor:x:43:
    mysql:x:89:
    Last edited by giuscri (2014-05-20 12:18:56)

    SidK wrote:You must have modified your torrc to print to that log file. systemd starts the service as the tor user (see /usr/lib/systemd/system/tor.service). So if if you want to log to a file the tor user must have write access to it. By default however tor it set to log to the journal, which doesn't require any special permissions.
    Yes. I did edit the torrc file since I wanted the log to be store in that file. Indeed
    ## Logs go to stdout at level "notice" unless redirected by something
    ## else, like one of the below lines. You can have as many Log lines as
    ## you want.
    ## We advise using "notice" in most cases, since anything more verbose
    ## may provide sensitive information to an attacker who obtains the logs.
    ## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
    #Log notice file /var/log/tor/notices.log
    ## Send every possible message to /var/log/tor/debug.log
    Log debug file /var/log/tor/debug.log
    ## Use the system log instead of Tor's logfiles
    Log notice syslog
    ## To send all messages to stderr:
    #Log debug stderr
    I missed the file systemd uses to choose who's the process owner.
    Course, I could edit /usr/lib/systemd/system/tor.service such that root will become the process owner; or, I could add the user I use everyday in the root group, then change the permission of /var/log/tor/debug.log such that it will be writable also for the folks in the root group.
    Yet they both seems to be a bit unsafe ...
    What is the best choice, to you guys?
    Thanks,

  • Arch logging errors (/var/logs)

    i got two problems i'd like to solve maybe their cause is the same.
    first: is global arch logging. that's my ls -l of /var/log/
    -rw-r--r-- 1 root root      0   Apr 21 11:27 acpid.log
    -rw-r--r-- 1 root root      0   Apr  7 22:13 acpid.log.1
    -rw-r--r-- 1 root root      0   Apr 21 11:27 auth.log
    -rw-r--r-- 1 root root      0   Apr  7 22:14 auth.log.1
    -rw-r--r-- 1 root root   1092 Nov  7 02:52 boot
    -rw------- 1 root root   1152 Mar 17 08:06 btmp
    drwxr-xr-x 2 root root     72 Nov  7 16:56 ConsoleKit
    -rw-r--r-- 1 root root      0    Apr  7 22:14 crond
    -rw-r--r-- 1 root root      0    Apr 21 11:27 daemon.log
    -rw-r--r-- 1 root root      0    Apr  7 22:18 daemon.log.1
    -rw-r--r-- 1 root root  39494 Apr 22 13:18 dmesg.log
    -rw-r--r-- 1 root root      0    Apr 21 11:27 errors.log
    -rw-r--r-- 1 root root      0    Apr  7 22:18 errors.log.1
    -rw-r--r-- 1 root root      0    Apr 21 11:27 everything.log
    -rw-r--r-- 1 root root      0    Apr  7 22:18 everything.log.1
    -rw------- 1 root root  32032 Apr 22 12:03 faillog
    drwxrwx--T 2 root gdm    1392 Apr 22 13:18 gdm
    drwxr-xr-x 2 root root    368 Apr 21 11:27 httpd
    -rw-r--r-- 1 root root      0 Apr 21 11:27 kernel.log
    -rw-r--r-- 1 root root      0 Apr  7 22:19 kernel.log.1
    -rw-r--r-- 1 root root 292292 Apr 22 12:03 lastlog
    -rw-r--r-- 1 root root      0 Apr 21 11:27 messages.log
    -rw-r--r-- 1 root root      0 Apr  7 22:19 messages.log.1
    drwxr-xr-x 2 root root     48 Feb 26 06:56 old
    -rw-r--r-- 1 root root 151881 Apr 22 13:42 pacman.log
    -rw-r--r-- 1 root root     86 Apr 22 13:18 pm-powersave.log
    -rw-r--r-- 1 root root   6049 Apr 20 10:21 pm-suspend.log
    -rw-r--r-- 1 root root      0 Apr 21 11:27 syslog.log
    -rw-r--r-- 1 root root      0 Apr  7 22:19 syslog.log.1
    -rw-r--r-- 1 root root      0 Apr 21 11:27 user.log
    -rw-r--r-- 1 root root      0 Apr  7 22:19 user.log.1
    -rw-rw-r-- 1 root root 407424 Apr 22 13:29 wtmp
    -rw-rw-r-- 1 root root 415488 Apr  7 18:36 wtmp.1
    -rw-r--r-- 1 root root  13947 Apr 22 13:18 Xorg.0.log
    -rw-r--r-- 1 root root  14486 Apr 22 13:17 Xorg.0.log.old
    all files, that have dublicate name with .1 at the end, are always empty and as time goes by files with the same name but with .2, .3, .4 appear but also empty. It looks like arch is trying to create logs but something goes wrong and nothing is logged.
    second: i got errors from cron if i do run-cron /etc/cron.daily/ related to log files:
    sudo run-cron /etc/cron.daily/
    error: syslog-ng:1 duplicate log entry for /var/log/crond.log
    error: found error in /var/log/messages.log /var/log/auth.log /var/log/mail.log /var/log/kernel.log /var/log/errors.log /var/log/daemon.log /var/log/user.log /var/log/iptables.log /var/log/everything.log /var/log/syslog.log /var/log/acpid.log /var/log/crond.log /var/log/lpr.log /var/log/uucp.log /var/log/news.log /var/log/ppp.log /var/log/debug.log , skipping
    looks like the files r corrupted or something. please help find out the reasons and fix things up.

    I think it has to do with the group log having write permissions...
    # ls -l /var/log/
    total 8240
    drwxr-xr-x 2 root root 4096 Mar 31 01:38 ConsoleKit/
    drwxr-xr-x 2 root root 4096 Apr 4 03:52 httpd/
    drwxr-xr-x 2 http http 4096 Apr 18 03:45 lighttpd/
    drwxr-xr-x 2 root root 4096 Feb 25 23:56 old/
    -rw-r----- 1 root log 29283 Apr 22 11:05 auth.log
    -rw-r----- 1 root log 71395 Apr 18 03:26 auth.log.1
    -rw-r----- 1 root log 62225 Apr 11 03:17 auth.log.2
    -rw-r----- 1 root log 121945 Apr 4 03:41 auth.log.3
    -rw------- 1 root root 0 Mar 29 02:00 btmp
    -rw-r----- 1 root log 6622 Apr 22 09:17 crond.log
    -rw-r----- 1 root log 10756 Apr 18 03:45 crond.log.1
    -rw-r----- 1 root log 10340 Apr 11 03:45 crond.log.2
    -rw-r----- 1 root log 8809 Apr 4 03:45 crond.log.3
    -rw-r----- 1 root log 63451 Apr 22 11:01 daemon.log
    -rw-r----- 1 root log 101060 Apr 18 03:42 daemon.log.1
    -rw-r----- 1 root log 103755 Apr 11 03:37 daemon.log.2
    -rw-r----- 1 root log 72875 Apr 4 03:36 daemon.log.3
    -rw-r--r-- 1 root root 32631 Apr 19 03:27 dmesg.log
    -rw-r----- 1 root log 2881 Apr 21 23:22 errors.log
    -rw-r----- 1 root log 162980 Apr 17 09:55 errors.log.1
    -rw-r----- 1 root log 30491 Apr 9 21:54 errors.log.2
    -rw-r----- 1 root log 31213 Apr 3 18:38 errors.log.3
    -rw-r----- 1 root log 276636 Apr 22 11:01 everything.log
    -rw-r----- 1 root log 1196453 Apr 18 03:45 everything.log.1
    -rw-r----- 1 root log 374844 Apr 11 03:45 everything.log.2
    -rw-r----- 1 root log 610588 Apr 4 03:45 everything.log.3
    -rw------- 1 root root 24144 Apr 22 10:25 faillog
    -rw-r----- 1 root log 185643 Apr 22 10:25 kernel.log
    -rw-r----- 1 root log 1051728 Apr 18 02:02 kernel.log.1
    -rw-r----- 1 root log 250567 Apr 11 03:27 kernel.log.2
    -rw-r----- 1 root log 521352 Apr 3 18:38 kernel.log.3
    -rw-r--r-- 1 root root 293752 Apr 22 10:25 lastlog
    -rw-r----- 1 root log 229278 Apr 22 11:01 messages.log
    -rw-r----- 1 root log 959109 Apr 18 03:42 messages.log.1
    -rw-r----- 1 root log 309842 Apr 11 03:37 messages.log.2
    -rw-r----- 1 root log 489801 Apr 4 03:36 messages.log.3
    -rw-r--r-- 1 root root 77695 Apr 22 10:42 pacman.log
    -rw-r--r-- 1 root root 86 Apr 19 13:23 pm-powersave.log
    -rw-r----- 1 root log 825 Apr 19 03:27 syslog.log
    -rw-r----- 1 root log 1387 Apr 15 15:39 syslog.log.1
    -rw-r----- 1 root log 738 Apr 9 11:36 syslog.log.2
    -rw-r----- 1 root log 1600 Mar 31 00:02 syslog.log.3
    -rw-r----- 1 root log 16287 Apr 22 10:15 user.log
    -rw-r----- 1 root log 24546 Apr 17 03:45 user.log.1
    -rw-r----- 1 root log 626 Apr 11 03:27 user.log.2
    -rw-r----- 1 root log 416 Mar 30 04:12 user.log.3
    -rw-r----- 1 root log 6622 Apr 22 09:17 uucp.log
    -rw-r----- 1 root log 10756 Apr 18 03:45 uucp.log.1
    -rw-r----- 1 root log 10340 Apr 11 03:45 uucp.log.2
    -rw-r----- 1 root log 8809 Apr 4 03:45 uucp.log.3
    -rw-rw-r-- 1 root root 471552 Apr 22 10:25 wtmp
    -rw-r--r-- 1 root root 150528 Apr 1 03:21 wtmp.1
    -rw-r--r-- 1 root wheel 16308 Apr 22 10:25 Xorg.0.log
    -rw-r--r-- 1 root users 23624 Apr 22 10:25 Xorg.0.log.old
    Did you chown -R root:root /var/log on Apr 7?

  • Permanently set /var/log/messages* to mode 644

    What process constantly changes /var/log/messages* mode back to 640? I want to disable that. Thanks.

    I would guess logrotate.  Have you checked /etc/logrotate.d/syslog?  Does it specify a particular permission there?
    If not specified, logrotate should retain the permissions of the existing file.
    Marc

  • Move /var/log to HDD from SSD

    Hi guys
    I just installed arch for the first time and made the mistake of having /var/log on my SSD. How do I "move" it to my HDD? Someone on #archlinux told me to symlink it but I don't know how to do that in a way so the logs get written directly to the HDD but not the SSD.
    Any ideas?

    I didn't much care when I set this box up about /var being on my SSD, but now I've been wondering. So, having had experience with moving filesystems in the past (/usr, /tmp, ...) on running machines I figured /var wouldn't be much problem. Here is what I did:
    First, I dual boot and the 2 HDD's are setup in RAID0 and are for local misc. storage so it was setup in only 2 partitions, 1 1GB one for Linux swap, and 1 massive partition for everything else. That big partition is for my misc. Windows stuff, so it's NTFS and unusable for the purpose at hand. I simply used GParted to slice off a 4GB piece at the end of the drive. This is what I will be using for /var.
    I then made a directory under / named 'var.tmp' (ie: /var.tmp). This I used for a temporary mount point for my new /var partition. I also edited my /etc/fstab to add in the new partition and mount point, ie: /dev/mapper/pdc_bggaahdef3 /var ext4 defaults,user_xattr,noatime 0 1
    From here I mounted the new partition on /var.tmp and ran the following command chain:
    cp -av /var/* /var.tmp && umount /dev/mapper/pdc_bggaahdef3 && mv /var /var.old && mkdir /var && mount /var
    So as fast as possible I'm copying the current contents of /var onto the new drive (using the archive flag which retains all permissions, symlinks, etc), unmounting that new drive (for later remounting), moving the current /var to /var.old (in case something bad happens or gets missed I can revert back), and finally re-making the /var directory and mounting the new drive.
    I did restart a few services just in case as I don't want to reboot at the moment, and confirmed via /var/run and /var/run/daemons that processes are still keeping track of themselves, and also /var/log is logging current events. The system seems happy, but any quirks encounted should be fixable by a reboot so everything can properly refresh.
    If you already have a mount on a HDD that you're using under Linux, instead of making a dedicated partition just for /var as I did, you could (as suggested) use the symlink method. This is basically just mv'ing /var to that partition and then ln -s /new/location/of/var /var
    Hope this helps!

  • ICal doesn't show delegation, and generates date and time error messages in /var/log/system.log

    I have a problem with my iCal, when I use my caldav account, I can only see my own calendar on my MBA, on my co-workers MBP it works fine with both my account and his. My co-worker can't see other calendars than his own when he uses iCal on my laptop.
    We can reproduce this problem on his computer by setting Location to Automatic rather than Amsterdam, then after deleting iCal's cache files, the caldav account and setting the Location back to Amsterdam solves the problem for him.
    It does not solve the problem for me (or several other co-workers). We've been looking at this for a few weeks, and we can not find any clear pattern why certain machines have this problem and others don't.
    All machines (both affected and unaffected) are running Mac OS 10.7.2 with iCal 5.0.1
    I've spoken to Apple support over the phone (in the Netherlands), unfortunately, they couldn't help with this.
    So far we've tried numerous location and language settings, but on affected machines nothing appears to solve the delegation problem (which we assume to be connected to the error messages iCal generates)
    Starting iCal yeilds the following error messages in /var/log/system.log:
    Jan  5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
    Jan  5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=3
              line 1,6: unexpected char: '='
    Jan  5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
    Jan  5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=10
              line 1,6: unexpected char: '='
    Jan  5 11:31:05 dhcp-91 iCal[23884]: Unexpected EOF, returning last token as fallback
    Jan  5 11:31:05 dhcp-91 iCal[23884]: VTIMEZONE does not match System Time Zone (Europe/Amsterdam) for 20100105T000000 to 20120105T000000: (
                  "interval: 2001-01-01 01:00:00 +0100, offset: 3600"
              ) != (
                  "interval: 2010-03-28 03:00:00 +0200, offset: 7200",
                  "interval: 2010-10-31 02:00:00 +0100, offset: 3600",
                  "interval: 2011-03-27 03:00:00 +0200, offset: 7200",
                  "interval: 2011-10-30 02:00:00 +0100, offset: 3600"
              BEGIN:VTIMEZONE
              X-LIC-LOCATION:Europe/Amsterdam
              TZID:Europe/Amsterdam
              BEGIN:DAYLIGHT
              TZOFFSETFROM:+0100
              TZNAME:CEST
              TZOFFSETTO:+0200
              DTSTART:19700329T020000
              END:DAYLIGHT
              BEGIN:STANDARD
              TZOFFSETFROM:+0200
              TZNAME:CET
              TZOFFSETTO:+0100
              DTSTART:19701025T030000
              END:STANDARD
              END:VTIMEZONE
    Jan  5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
    Jan  5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=3
              line 1,6: unexpected char: '='
    Jan  5 11:31:05 dhcp-91 [0x0-0x58f58f].com.apple.iCal[23884]: line 1,1: expecting FREQUENCE, found 'BYDAY' as token type 5
    Jan  5 11:31:05 dhcp-91 iCal[23884]: iCalendar recurrence failure BYDAY=-1SU;FREQ=YEARLY;BYMONTH=10
              line 1,6: unexpected char: '='
    Jan  5 11:31:05 dhcp-91 iCal[23884]: Unexpected EOF, returning last token as fallback
    Jan  5 11:31:05 dhcp-91 iCal[23884]: VTIMEZONE does not match System Time Zone (Europe/Amsterdam) for 20100105T000000 to 20120105T000000: (
                  "interval: 2001-01-01 01:00:00 +0100, offset: 3600"
              ) != (
                  "interval: 2010-03-28 03:00:00 +0200, offset: 7200",
                  "interval: 2010-10-31 02:00:00 +0100, offset: 3600",
                  "interval: 2011-03-27 03:00:00 +0200, offset: 7200",
        "interval: 2011-10-30 02:00:00 +0100, offset: 3600"
              BEGIN:VTIMEZONE
              X-LIC-LOCATION:Europe/Amsterdam
              TZID:Europe/Amsterdam
              BEGIN:DAYLIGHT
              TZOFFSETFROM:+0100
              TZNAME:CEST
              TZOFFSETTO:+0200
              DTSTART:19700329T020000
              END:DAYLIGHT
              BEGIN:STANDARD
              TZOFFSETFROM:+0200
              TZNAME:CET
              TZOFFSETTO:+0100
              DTSTART:19701025T030000
              END:STANDARD
              END:VTIMEZONE
    And when I close iCal I get:
    Jan  5 11:33:25 dhcp-91 [0x0-0x592592].com.apple.iCal[23894]: token mismatch: 4 != 5

    I'm seeing the same thing, and I can't even find where OS X stores calendars on disk anymore...

  • Hard Drive filling up: SubmitDiagInfo, /private/var & log issues

    This topic is part question, part help for people I've seen having a similar problem in other threads. My issue is different enough from the other issues, that I wanted to post it as a separate topic.
    I've had about 24GB of available space for weeks now. I haven't downloaded any large files recently, nor created any myself.
    Suddenly I noticed the hard drive space decreasing. I went from 24GB, to 19GB, to 10GB, then 8, 5, 1.5... next thing I knew, it said I had 260MB available. This was within maybe two days, with a big ramp-down within a couple of hours this morning, while I was on a train, and not even connected to a network.
    I started getting error messages saying my hard drive was full; then, I got errors saying I didn't have enough application memory, and applications were being paused, and I would have to force quit them. Within about 5 minutes, I dropped from 1.5GB to 260MB.
    Thinking back, the last week or so, I remembered that sometimes when I came into my office in the morning, my Mac would be awake (I usually sleep it at the end of the day, and an error message would be displayed saying SubmitDiagInfo had crashed. I thought this might have something to do with it.
    I did some detective work in these forums. I checked Activity Monitor and the Console. Sure enough, SubmitDiagInfo was taking up a bunch of CPU time.
    The Console revealed I had a lot of Diagnostic Logs. I tried deleting them with the Console's Clear button, but it didn't seem to do anything. I checked with OmniDiskSweep, and sure enough, I had over 20GB of log files.
    At this point, my hard drive was so full, I had to force quit OmniDiskSweep. I used the Go To Folder command and entered /private/var/log - The Diagnostic Logs folder was nearly 20GB. I deleted it and emptied the trash immediately.
    I looked at the /private/var/vm folder and noticed it was also very large (10GB), but I had read elsewhere not to mess with this folder.
    From the console, I quit SubmitDiagInfo.
    I check my hard drive, and I'm suddenly back to 24GB free space.
    When I look again at /private/var/vm, and sure enough it is 5GB smaller.
    This is weird stuff, and I hope this description helps anyone else having this problem.
    What's interesting is, because the /private folder is invisible, you can't use it to calculate your disk space usage. For example, the folders on my drive had the following space usage:
    62.46GB34.53GB+22.96GB+4.78GB4.02GB = 128.75GB (plus a few "small" folders with maybe 300MB)
    Since the drive showed 159GB total space available, I couldn't figure out where the other 30GB was.
    Once I found /private/log, I could see it had 19.29GB:
    62.4634.53+22.96+4.78+4.0219.29 = 148.04 - ah, this makes more sense, but I'm still missing 10GB! So, I look at /private/vm, and boom, there is the extra 10.6GB hiding. All 159GB present and accounted for.
    The question I have is, of course, can anyone explain why this is happening, so I can prevent it from happening again?
    I hope someone finds this helpful.

    Thanks... that is helpful. I have Carbon Copy Cloner, not
    Super Duper, so I will keep that solution in mind.
    Do not, repeat do not, clone your current suspect hard drive
    to your CCC backup. That would defeat the purpose of having
    a good backup. I don't know if you can boot from you CCC
    backup. That would be a good test. I was able to boot from
    my SuperDuper backup and notice normal hard drive space.
    In the meantime, I ran the extended system test, and the
    computer passed.
    Mine with the growing hard drive passed every test I had plus
    the test Apple recommended. They were quick place the blame
    on a Virtual Windows XP Pro. I do not thing that was the
    problem. My normal Macintosh HD is usually about 52 GB
    and it was showing 110 GB used and I never could figure out
    what was hogging the hard drive.
    Good luck!

  • ERROR messages in /var/log/messages

    Hi,
    I encountered a error messages in /var/log/messages please find below
    Dec 9 04:03:08 drs syslogd 1.4.1: restart (remote reception).
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:03:18 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:03:18 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    Dec 9 04:08:19 drs logger: Could not access /etc/oracle/scls_scr/drs/root/crsstart.
    Dec 9 04:08:19 drs init: Id "h1" respawning too fast: disabled for 5 minutes
    Dec 9 04:10:46 drs rpc.mountd: authenticated unmount request from 10.3.141.26:651 for /opt/backup_log/srv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:657 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated unmount request from 10.3.141.26:672 for /opt/backup_log/websrv (/opt/backup_log)
    Dec 9 04:10:47 drs rpc.mountd: authenticated mount request from 10.3.141.26:677 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:12:01 drs rpc.mountd: authenticated unmount request from 10.3.141.26:849 for /opt/backup_log/ws (/opt/backup_log)
    Dec 9 04:13:20 drs logger: Oracle Cluster Ready Services disabled by corrupt install
    and database (oracle 10g) is running fine, but i cant figure out what could be the problem, can anyone just help me out on this.
    Jafar

    Hi,
    #h1:35:respawn:/etc/init.d/init.cssd run >/dev/null 2>&1 </dev/null
    by commenting above line in initttab file would stop messaging, is this would have any adverse affect on the database. As its a production server, so i am really taking time to resolve it. Your suggestions are welcome. If there is no harm in commenting the above line then i would go forward to comment that line.
    Thanks
    Jafar>

  • Errors in a log file /var/log/system.log

    I'm getting these errors in a log file /var/log/system.log
    Shutdown:
    Sep 21 12:41:38 Mac-mini.local WindowServer[86]: CGXGetConnectionProperty: Invalid connection 42243
    Sep 21 12:41:38 Mac-mini.local coreservicesd[58]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=145
    Sep 21 12:41:38 Mac-mini.local WindowServer[86]: CGXGetConnectionProperty: Invalid connection 42243
    Sep 21 12:41:38 Mac-mini.local coreservicesd[58]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to Sep 21 12:41:38 Mac-mini.local loginwindow[41]: DEAD_PROCESS: 41 console
    Sep 21 12:41:38 Mac-mini.local WindowServer[86]: CGXGetConnectionProperty: Invalid connection 42243
    Sep 21 12:41:38 Mac-mini.local coreservicesd[58]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=142
    Sep 21 12:41:38 Mac-mini.local shutdown[300]: halt by andrei:
    Boot & Working:
    Sep 21 12:42:11 localhost com.apple.launchd[1] (com.apple.automountd): Unknown key for boolean: NSSupportsSuddenTermination
    Sep 21 12:42:22 Mac-mini.local apsd[56]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
    Sep 21 12:42:26 Mac-mini.local authorizationhost[121]: in od_principal_for_user(): failed: 7
    Sep 21 12:42:26 Mac-mini.local authorizationhost[121]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
    Sep 21 12:42:27 Mac-mini.local loginwindow[41]: ERROR | ScreensharingLoginNotification | Failed sending message to screen sharing GetScreensharingPort, err: 1102
    Sep 21 12:42:31 Mac-mini.local XProtectUpdater[24]: Ignoring new signature plist: Not an increase in version
    Sep 21 12:42:32 Mac-mini com.apple.launchd[1] (com.apple.xprotectupdater[24]): Exited with code: 252
    Sep 21 12:43:04 Mac-mini.local com.apple.security.pboxd[290]: Bug: 12C54: liblaunch.dylib + 23849 [2F71CAF8-6524-329E-AC56-C506658B4C0C]: 0x25
    Sep 21 12:53:49 Mac-mini.local CVMServer[98]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
    Sep 21 12:59:48 Mac-mini.local com.apple.security.pboxd[290]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
    Sep 21 13:00:07 Mac-mini.local com.apple.security.pboxd[290]: _NXTermWindow: error releasing window (1000)
    Sep 21 13:00:07 Mac-mini.local com.apple.security.pboxd[290]: __block_global_2: connection failed unexpectedly; terminating process; delegate was (
    system.log - https://docs.google.com/open?id=0Bz5zKwys0GTcSzI5UFJRUzFxZjQ

    File a bug report with Apple.

  • Errors in /var/log/alf.log?

    When I look in /var/log/alf.log all I see is entries like this:
    SecCodeCreateWithPID error:: No such process
    What does it mean?
    socketfilterfw shows up in the Activity Monitor, so it appears that Apple's application firewall is not completely dead. How would I best test whether it is functioning properly?
    Glenn

    1) lxdm is in /usr/sbin
    [dean@PsyMadness ~]$ which lxdm
    /usr/sbin/lxdm
    2) AFAIK lxdm does not use .xinitrc
    edit: Maybe you are trying to run /usr/bin/lxdm (which doesn't exist) in inittab and the correct one in DAEMONS in rc.conf
    Last edited by Terminator (2012-05-30 09:05:54)

  • 2 TB MyCloud filesystems "/tmp" and "/var/log" both at 100%

    Now, this is just plain weird...  here's the output from "df -k": Filesystem 1K-blocks Used Available Use% Mounted on
    rootfs 1968336 685956 1182392 37% /
    /dev/root 1968336 685956 1182392 37% /
    tmpfs 40960 20992 19968 52% /run
    tmpfs 40960 64 40896 1% /run/lock
    tmpfs 10240 0 10240 0% /dev
    tmpfs 5120 0 5120 0% /run/shm
    tmpfs 102400 102400 0 100% /tmp                                           <<<<<<<<<<<<<---------------
    /dev/root 1968336 685956 1182392 37% /var/log.hdd
    ramlog-tmpfs 20480 20480 0 100% /var/log                             <<<<<<<<<<<<<---------------
    /dev/sda4 1918220368 26235484 1853008884 2% /DataVolume
    /dev/sda4 1918220368 26235484 1853008884 2% /CacheVolume
    /dev/sda4 1918220368 26235484 1853008884 2% /nfs/TimeMachineBackup
    /dev/sda4 1918220368 26235484 1853008884 2% /nfs/Public
    /dev/sda4 1918220368 26235484 1853008884 2% /nfs/SmartWare (pls. excuse the formatting but you can see at the arrows that /var/log and /tmp are at 100%) "/tmp" is filling up with *hundreds* of files with the form -rw------- 1 www-data www-data 0 Jul 14 00:43 sess_pdh5c9g907vqvusb3mdsvtlum3
    -rw------- 1 www-data www-data 0 Jul 14 00:43 sess_2a7v2di677ra43sh76lonm3de1
    -rw------- 1 www-data www-data 0 Jul 14 00:43 sess_o6kh3i4iggg78evs53kp6enpf6
    -rw------- 1 www-data www-data 0 Jul 14 00:43 sess_o0ahso52sef3h0if3ifpo4dno3
    -rw------- 1 www-data www-data 0 Jul 14 00:43 sess_bvn1o9v4b4ldgoq9uvtn2n24i0-rw------- 1 www-data www-data 0 Jul 14 00:43 sess_h01fbr9o1pte3ud2s9ainth7b6 all similarly named "sess_[somethingorother] And "/var/log" is filling up due to file "/var/log/user.log", with gazillions of error messages of the form Jul 14 00:02:06 WDMyCloud REST_API[6751]: 192.168.1.101 ORION_LOG /var/www/rest-api/api/Auth/src/Auth/User/UserSecurity.php ISAUTHENTICATED [ERROR] dbgvar0: Array\n(\n [_] => 1436857244438\n [RequestScope] => RequestScope Object\n (\n )\n\n)\n and file "/var/log/apache2/error.log", that has more gazillions of error messages in it of the form [Tue Jul 14 00:07:25.715561 2015] [:error] [pid 7107] [client 192.168.1.101:3844] PHP Fatal error: Uncaught exception 'Zend\\Log\\Exception\\RuntimeException' with message 'No log writer specified' in /var/www/rest-api/lib/Zend/Log/Logger.php:245\nStack trace:\n#0 /var/www/rest-api/lib/Zend/Log/Logger.php(396): Zend\\Log\\Logger->log(4, 'Unknown: open(/...', Array)\n#1 [internal function]: Zend\\Log\\Logger::Zend\\Log\\{closure}(2, 'Unknown: open(/...', 'Unknown', 0, Array)\n#2 {main}\n thrown in /var/www/rest-api/lib/Zend/Log/Logger.php on line 245 ooookay... something has clearly gone bezoomny...  Anybody seen this?  before I go off on Yet AnotherMad Debian Bug Hunt?  

    Hey WD...  Y'all's got a BUG... When I access the MyClod from my laptop running XP with FireFox, I get the thousands of  "sess_*" files written to /tmp, and I get groups of messages of the form Jul 14 22:36:26 WDMyCloud REST_API[23951]: 192.168.1.101 ORION_LOG /var/www/rest-api/api/Auth/src/Auth/User/UserSecurity.php ISAUTHENTICATED [ERROR] Authentication failure for /api/2.1/rest/mediacrawler_status?_=1436938574613
    Jul 14 22:36:26 WDMyCloud REST_API[23951]: 192.168.1.101 ORION_LOG /var/www/rest-api/api/Auth/src/Auth/User/UserSecurity.php ISAUTHENTICATED [ERROR] dbgvar0: Array\n(\n [_] => 1436938574613\n [RequestScope] => RequestScope Object\n (\n )\n\n)\n
    Jul 14 22:36:26 WDMyCloud REST_API[23951]: 192.168.1.101 ORION_LOG /var/www/rest-api/api/Auth/src/Auth/User/UserSecurity.php ISAUTHENTICATED [ERROR] dbgvar0: Array\n(\n [_] => 1436938574613\n [RequestScope] => RequestScope Object\n (\n )\n\n)\n written to /var/log/user.log. But when I access it similarly from the desktop machine, also running XP with FireFox, I just get *one* of the "sess_*" whatever files written to /tmp, and just one set of messages of the form Jul 14 22:40:26 WDMyCloud REST_API[24325]: 192.168.1.100 OUTPUT DlnaServer\Controller\Database GET SUCCESS
    Jul 14 22:40:29 WDMyCloud REST_API[23952]: 192.168.1.100 OUTPUT System\Configuration\Controller\FactoryRestore GET SUCCESS
    Jul 14 22:40:29 WDMyCloud Zend\Log[23877]: 8192
    Jul 14 22:40:51 WDMyCloud REST_API[23952]: 192.168.1.100 OUTPUT Alerts\Controller\Alerts GET SUCCESS written to /var/log/user.log. So the MyClod is playing nice with some computers and not others... My guess is this could be happening more than WD knows about and could be producing all manner of mysterious behavior, since not only does it only happen on some machines but it does *not* crash the MyClod - at least not right away.  The main effect is to fill /tmp and /var/log with garbage so nothing can write to them, which will probably affect some things and not others... https://www.youtube.com/embed/2Gwnmb6P-3k  

Maybe you are looking for