[solved] netatalk / afpd faulting

First let me state that this was working flawlessly up until (as best I can tell) around 1:30pm today. I set up my Arch server to have netatalk/afp serving storage to the Macs in my house. For some reason now the logs are throwing all kinds of errors and the servers are simply not starting.
Here is what it looked like prior to the fail:
$ head -n 50 /var/log/afpd.log [21:15:58]
Jan 29 17:20:16.875697 afpd[17970] {afp_mdns.c:212} (E:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65537
Jan 29 17:30:18.407428 afpd[18015] {afp_mdns.c:212} (E:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65537
Jan 29 17:33:37.391282 afpd[18031] {afp_mdns.c:212} (E:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65537
Jan 30 10:08:15.577188 afpd[647] {afp_mdns.c:212} (E:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65537
Mar 12 01:15:25.771260 afpd[15232] {afp_mdns.c:212} (E:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65537
Mar 14 18:09:43.818452 afpd[15237] {afp_dsi.c:319} (E:AFPDaemon): afp_alarm: child timed out, entering disconnected state
Mar 15 18:08:14.119215 afpd[15237] {afp_dsi.c:311} (E:AFPDaemon): afp_alarm: reconnect timer expired, goodbye
Mar 31 23:30:46.092706 afpd[6689] {dsi_tcp.c:192} (E:DSI): dsi_tcp_open: invalid header
Mar 31 23:30:46.101109 afpd[6690] {dsi_tcp.c:192} (E:DSI): dsi_tcp_open: invalid header
Apr 23 04:34:53.214474 afpd[566] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 04:34:53.214929 afpd[566] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 04:34:55.334625 afpd[566] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 04:34:55.334694 afpd[566] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 06:19:57.225049 afpd[3959] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 06:19:57.225538 afpd[3959] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 06:20:00.351332 afpd[3959] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 06:20:00.351414 afpd[3959] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 08:17:26.401149 afpd[483] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 08:17:26.401536 afpd[483] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 08:17:28.914161 afpd[483] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
Apr 23 08:17:28.914236 afpd[483] {ad_flush.c:293} (E:Default): sys_lsetxattr("/mnt/data/."): Permission denied
The permission denies are probably from when it was trying to access the share before it was mounted.
Anyway, now the immediate next entry in the log is from today when it starts failing:
May 07 13:22:35.641383 afpd[24379] {fault.c:123} (S:Default): ===============================================================
May 07 13:22:35.641848 afpd[24379] {fault.c:124} (S:Default): INTERNAL ERROR: Signal 11 in pid 24379 (3.1.0)
May 07 13:22:35.641895 afpd[24379] {fault.c:125} (S:Default): ===============================================================
May 07 13:22:35.643156 afpd[24379] {fault.c:96} (S:Default): PANIC: internal error
May 07 13:22:35.643200 afpd[24379] {fault.c:97} (S:Default): BACKTRACE: 11 stack frames:
May 07 13:22:35.643229 afpd[24379] {fault.c:103} (S:Default): #0 /usr/lib/libatalk.so.12(netatalk_panic+0x24) [0x7f19c2d28624]
May 07 13:22:35.643257 afpd[24379] {fault.c:103} (S:Default): #1 /usr/lib/libatalk.so.12(+0x38758) [0x7f19c2d28758]
May 07 13:22:35.643283 afpd[24379] {fault.c:103} (S:Default): #2 /usr/lib/libc.so.6(+0x33df0) [0x7f19c212bdf0]
May 07 13:22:35.643309 afpd[24379] {fault.c:103} (S:Default): #3 /usr/lib/libc.so.6(_IO_vfprintf+0x38a7) [0x7f19c2140ac7]
May 07 13:22:35.643335 afpd[24379] {fault.c:103} (S:Default): #4 /usr/lib/libc.so.6(__vasprintf_chk+0xb5) [0x7f19c21f1875]
May 07 13:22:35.643360 afpd[24379] {fault.c:103} (S:Default): #5 /usr/lib/libc.so.6(__asprintf_chk+0x82) [0x7f19c21f17b2]
May 07 13:22:35.643386 afpd[24379] {fault.c:103} (S:Default): #6 /usr/bin/afpd() [0x40db92]
May 07 13:22:35.643411 afpd[24379] {fault.c:103} (S:Default): #7 /usr/bin/afpd(configinit+0x4d1) [0x40bfe1]
May 07 13:22:35.643436 afpd[24379] {fault.c:103} (S:Default): #8 /usr/bin/afpd(main+0x39b) [0x40b1cb]
May 07 13:22:35.643461 afpd[24379] {fault.c:103} (S:Default): #9 /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f19c2118000]
May 07 13:22:35.643487 afpd[24379] {fault.c:103} (S:Default): #10 /usr/bin/afpd() [0x40b9b2]
Now that is just repeating over and over again. Anyone else seeing anything like this? Any ideas?
I've tried rebooting the server, etc..
Last edited by lifeafter2am (2014-05-08 06:38:31)

I'm an idiot, nevermind me. I need to keep better track of what packages are from the AUR and update them more frequently; I always forget to run updates on AUR packages. Obviously an update in the past few days broke this, but there was already an update to the netatalk package on the AUR. I updated this package and it appears to be working now. I can't test it fully until I get home, but I think this solved it.
Going to mark as solved for now.

Similar Messages

  • [Solved] pSX Segmentation Fault - [Partially Solved] pSX problems

    Alright, I think that I've solved the segmentation fault thing that was happening in pSX whenever I ran it (I use Arch x86_64).  I'm not sure what was wrong, but after installing lib32-intel-dri-7.11.2-2 via pacman pSX appeared to work fine.  The only other problems I've encountered so far is that (1) installing one of the alsa plugin things (not sure which one since I was installing more than one at the time) seems to make it crash and stay crashed as long as the plugins are installed, (2) another problem was that when I try to load a savestate while running a loaded savestate of Final Fantasy 7 in pSX (I say FF7 because that's the only game I've tried playing so far) causes pSX to crash with a segmentation error, (3) and the last problem, which does happen to be the least important/crippling is that while pSX is running I keep getting a message displayed to xterm saying: "sound: underrun".  That's pretty much it.  So if any of you have been having trouble getting pSX to run on an x86_64 install of Arch/have been getting segmentation fault errors when you try to run pSX on Arch x86_64 just install lib32-intel-dri or the applicable alternative and it should hopefully work.
    Last edited by Orodruin (2012-01-06 09:44:00)

    I ran into this same problem after an upgrade on a Thinkpad T60 and this did fix the problem.
    Thanks to Roxas for posting the solution.

  • [solved] fontforge seg faults on failure to find font

    I'm having what I suspect is a fairly standard problem but I've been unable to track it down using google, a forum search or the wiki.
    Basically, fontforge seg faults on start. More specifically, it displays the dialog which allows me to select the font I want to open and then crashes. Starting the application from the command line produces this:
    $ fontforge
    Copyright (c) 2000-2012 by George Williams.
    Executable based on sources from 14:57 GMT 31-Jul-2012-ML-D.
    Library based on sources from 14:57 GMT 31-Jul-2012.
    Help! Server claimed font
    -adobe-courier std-medium-r-normal--16-0-0-0-m-0-iso10646-1
    existed in the font list, but when I asked for it there was nothing.
    I may crash soon.
    Segmentation fault (core dumped)
    I've tried fc-cache both with and without -f as both root and me. I've also tried moving ~/.fontconfig and ~/.config/fontconfig to backups and creating empty directories in their places. I've also recreated every fonts.dir and fonts.scale which locate can find on my system. I've also grepped "adobe-courier" in all of these files, all copies of fonts.alias found by locate and through /var/cache/fontconfig/* and not found any trace. I've examined (as best I can but this is not saying very much) the font config under /etc/fonts/.
    The only even vaguely relevant information I've found references a fedora/red hat bug from two or three years ago and those bugs were marked as solved by updates and closed in fedora 10/11.  (Fedora is currently at 17.) Moreover, the problems there were traced to fonts.{dir,scale} not being updated and I've recreated all of these files as found by locate so they should all be current.
    I'm sure I'm missing the stunningly obvious. Can anybody tell me where this reference might be coming from? Or otherwise suggest what I'm missing?
    I haven't needed fontforge for a while so I don't know when it ceased to work and this is not helping with troubleshooting.
    Last edited by cfr (2012-12-14 00:11:37)

    The error may be caused by a bad entry in a fonts.dir file in one of your font directories. This file is used by an older method than fontconfig to index fonts for apps in X.
    I would use 'locate' to find all files named fonts.dir. (There is probably a better way to find these files than 'locate'). When the files are found, 'grep' can be used to find the one with the bad entry. The following line of combined commands should work:
    $ for file in $(locate fonts.dir); do grep -l 'adobe-courier std' $file; done
    Then navigate to that file's directory and run:
    $ mkfontscale
    $ mkfontdir
    Finally, as root, run
    # xset fp rehash
    See https://wiki.archlinux.org/index.php/Fo … plications.

  • Cnid problem with netatalk afpd

    Hey,
    I just setup netatalk from AUR as stated in the wiki. Everything works fine, but i get an error message, when I try to connect from my MacBook.
    "Something wrong with the volume's CNID DB, using temporary CNID DB instead. Check server messages for details!"
    Where can I find the log-files for afpd? How can I fix this?

    if you started the afpd daemon without cnid_metad (cnid), then nothing is handling the database of file attributes. in the newest version of the package this is handled automatically by the "netatalk" daemon.

  • [SOLVED]Easytag Segmentation fault with kde3 (kdemod)

    (easytag:4811): Gtk-WARNING **: libbonoboui-2.so.0: cannot open shared object file: No such file or directory
    (easytag:4811): Gtk-WARNING **: libbonoboui-2.so.0: cannot open shared object file: No such file or directory
    EasyTAG 2.1.5: Abnormal exit! (PId: 4811).
    Received signal SIGSEGV (11)
    You have probably found a bug in EasyTAG. Please, send a bug report with a gdb backtrace ('gdb easytag core' then 'bt' and 'l') and informations to reproduce it to [email protected]
    Segmentation fault
    If I start up easytag while running KDE3 (kdemod), I get this problem every time. I have tried running it with openbox and it runs without a problem. I have deleted .easytag and reinstalled, but the problem continues.
    EDIT: Installing libbonoboui resolves the problem. It looks like the there is a dependency issue here, I'll file a bug.
    Last edited by alleyoopster (2008-08-02 17:18:06)

    Allan wrote:Do a "pacman -S libbonoboui" an all should be good.  I don't understand why this only occurs in KDEmod though.  Is that on two different computers.   File a bug report about the missing dependancy.
    Yeah thanks Allan, I figured it out. Bug report at http://bugs.archlinux.org/task/11094
    No it is on the same machine
    Last edited by alleyoopster (2008-08-02 17:18:28)

  • [Solved] Vlc seg faults after latest upgrade

    When updating vlc I now get this message  from pacman
    /tmp/alpm_LHUeqA/.INSTALL: line 1: 1809 Segmentation fault (core dumped) usr/lib/vlc/vlc-cache-gen -f /usr/lib/vlc/plugins
    Running vlc outputs
    VLC media player 2.0.6 Twoflower (revision 2.0.6-0-gbe9623c)
    Segmentation fault (core dumped)
    running dmesg gives
    segfault at 7fcfb5413e8b ip 00007fcfba60c206 sp 00007ffff597e588 error 4 in libc-2.17.so[7fcfba58c000+1a3000]
    I've tried manually running vlc-cache-gen as well, but I get the same output as above.  Downgrading vlc also resulted in the same error.  I am using the nvidia closed source driver if that makes a difference.  Any one have any ideas on whats going on here?
    Last edited by piratebill (2013-05-15 18:52:50)

    piratebill wrote:
    pilotkeller wrote:
    I hate to be 'that guy' but trying out mplayer2 is another option.
    I moved away form VLC over a year ago and haven't looked back.
    It's your call but I have VLC on Windows and the new versions seem to brick itself.
    Could be that it's old configs are breaking the new version.
    I'm not married to VLC, so noted.
    On the trying to repair it front, I found a german guy with the same issue:
    https://bbs.archlinux.de/viewtopic.php?pid=304355
    While google translate does try, I cant really tell what he did to fix it.  Thoughts?
    What he did was restore a system backup from a few days ago, then first a `pacman -Sy` to update the package list and after that a single `pacman -S vlc` so that only vlc gets updated, and then finally the system upgrade `pacman -Su`. Seems like that worked for him.
    Unfortunately I'm having the same problem and don't have the option to restore a recent system backup.

  • [SOLVED] netatalk and postfix init scripts (not systemd)

    Hey, does anybody have an older version of Arch running somewhere?
    I'm looking for init scripts for netatalk and postfix that I've just re-built from ABS on an outdated Arch system. However, both packages offer systemd support these days and no love for dissidents like myself.
    They are probably very simple to write on one's own, but I just want to make sure I don't overlook some important trick.
    If someone could possibly post those either here or on dpaste.org or whatever paste service you love, I would be a very happy person lol
    Last edited by iliv (2013-12-01 14:17:00)

    netatalk is in the AUR https://aur.archlinux.org/packages/netatalk/
    postfix: https://projects.archlinux.org/svntogit … a3365f273e

  • [solved] netatalk for Time Machine Backup

    Hi People,
    I currently have a problem getting a Mac being backup'd to my Arch Server box running netatalk. I installed netatalk via yaourt and changed the configuration file /etc/afp.conf
    ; Netatalk 3.x configuration file
    [Global]
    ; Global server settings
    hosts allow = 192.168.3.0/24
    [TimeMachine]
    path = /mnt/timemachine
    valid users = cjurk
    time machine = yes
    ; [Homes]
    ; basedir regex = /xxxx
    ; [My AFP Volume]
    ; path = /path/to/volume
    I've launched netatalk by using "systemctl start netatalk", but my Mac is not able to find the Backup volume within Timemachine. What can I do to get this working?
    Update: I tried multiple thing to get it working. OS X was telling me "Unsupported version" every time I tried to access a file share from netatalk. Seems like there is something not working. Afterwards I replaced netatalk with netatalk-ddp from AUR and now it works. Sadly, the -ddp package seems not to be systemd-ready yet.
    Last edited by commx (2012-11-17 14:37:13)

    Photographicality wrote:
    I would rather have two backups than one.
    Always prudent
    That's what I was trying to explain to Chris. With the screen cracked, it's not much use as a portable A/V device (especially the video). But it makes a great portable hard drive. Although, if I were you, I'd always be mindful that it's a hard-drive and not a flash-drive. I notice that most people with iPod-sized portable HD's tend to be a whole lot more cavalier about them than they would an iPod.
    It's always better to use it as a backup rather than a portable HD, if only for the reason that movement + spinning hard-disc = bad combination. Even the iPod's HD's which are designed for movement, aren't completely safe from problems.
    Anyway, good luck with your new iPodHD.

  • [Partially solved]Torcs Segmentation fault

    Everything working until I start race,text shows on screen and when it show 'Ready.' application crushes. I can change options and customize race,it working. I tried all races but it is same. I use nvidia-96xx proprietary driver.This is terminal output:
    [nale@nale ~]$ torcs
    Visual Properties Report
    Compatibility mode, properties unknown.
    /usr/bin/torcs: line 53: 12670 Segmentation fault (core dumped) $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
    Comp specs:
    processor: AMD 1.5 GHz
    ram: 256 MB
    video: nvidia  GeForce4 MX 4000 with 64MB
    Last edited by na12 (2013-02-21 10:04:41)

    Hi Gurus,
    glxgears and other openGL apps work fine, but Torcs (self-compiled) fails on startup:
    ~$ torcs
    Visual Properties Report
    Compatibility mode, properties unknown.
    /usr/local/bin/torcs: line 53: 4267 Segmentation fault $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*
    ~$
    and here the debug output:
    ~$ torcs -d
    GNU gdb (GDB) 7.4.1-debian
    Copyright (C) 2012 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/gdb/bugs/>...
    Reading symbols from /usr/local/lib/torcs/torcs-bin...done.
    (gdb) Starting program: /usr/local/lib/torcs/torcs-bin -l /home/peter/.torcs -L /usr/local/lib/torcs -D /usr/local/share/games/torcs
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    Visual Properties Report
    Compatibility mode, properties unknown.
    [New Thread 0x7fffee823700 (LWP 4343)]
    [New Thread 0x7fffee022700 (LWP 4344)]
    Program received signal SIGSEGV, Segmentation fault.
    0x00007fffeeeac773 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
    (gdb) #0 0x00007fffeeeac773 in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
    #1 0x00007ffff6b446d1 in getGLTextureMaxSize (result=@0x7ffff6d4ad14: 0)
    at glfeatures.cpp:113
    #2 0x00007ffff6b447d8 in checkGLFeatures () at glfeatures.cpp:155
    #3 0x00007ffff6b3c554 in GfScrInit (argc=7, argv=0x7fffffffe2f8)
    at screen.cpp:413
    #4 0x000000000040153c in main (argc=7, argv=0x7fffffffe2f8) at main.cpp:132
    (gdb) quit
    A debugging session is active.
    ---Type <return> to continue, or q <return> to quit---
    Inferior 1 [process 4340] will be killed.
    Quit anyway? (y or n) [answered Y; input not from terminal]
    ~$
    Any idea how I can fix the segmention fault?
    Things I've tried:
    - my user is in the 'video' group
    - I have not found any way to disable sound, since startup fails. I think from Debug that the sound isn't the issue.
    Thanks!

  • Sync/Async bridge via JMS with FAULT messages

    Hello all,<br><br>
    I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine.<br>
    But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion.<br><br>
    [SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled:<br><br>
    <pre>if(fault != null && faultNamespace != null)
      if(faultNamespace.equals("http://sap.com/xi/XI/System"))
        ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
        ((XIMessage)message1).setError(fault, "no additional information");
      } else
        ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
        ErrorInfo errorinfo = message1.createErrorInfo();
        errorinfo.setAttribute("ApplicationFaultInterface", fault);
        errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
        errorinfo.setAttribute("ErrorCode", fault);
        errorinfo.setAttribute("AdditionalErrorText", "no additional information");
        message1.setErrorInfo(errorinfo);
    } else
      ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
    }</pre><br>
    The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault.<br>
    Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception:<br><br>
    java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
    com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
    com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
    com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
    com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
    com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
    <br><br>
    Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
    <br><br>
    Thank you ...<br>
    Regards
    Tomas

    Hello again,
    I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
    2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
    2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
    2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
    2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
    I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
    com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
    which is generated.
    Any ideas or comments ?
    Thank you in advance.
    Regards
    Tomas

  • [SOLVED] projectM doesn't start

    Hello,
    today I realized that "projectM-pulseaudio" doesn't start anymore, I get the following error:
    projectM-pulseaudio: error while loading shared libraries: libGLEW.so.1.5: cannot open shared object file: No such file or directory
    Can anybody confirm this or give me a hint how to solve it?
    Thanks,
    matse
    Last edited by matse (2011-07-10 14:20:11)

    Problem solved, obviously my fault, projectm-pulseaudio is a package that I installed from AUR (I thought it is part of projectm from community), so recompiling solved the problem.
    matse

  • Solaris 11 Express - upgrade netatalk

    Hello,
    what is the safest way / procedure tu go from netatalk 2.1.x to 2.2.x ?
    Would a new boot environment prevent mishaps ?
    Thanks

    Ok,
    here is a short how to:
    install like here:
    http://marcoschuh.de/wp/?p=839
    I compiled without avahi support
    I had to
    svcadm disable network/dns/multicast:default
    svcadm disable system/avahi-bridge-dsd:default
    and re-enable avahi at some point
    AFP config files:
    /usr/local/etc/netatalk/
    afpd.conf
    - -tcp -noddp -uamlist uams_dhx2_passwd.so -nosavepassword
    the original entry of uams_dhx2.so is a symbolic link which doesn't seem to work...
    AppleVolumes.default
    add the option "options:tm" for Time Machine in Mac OS X Lion
    ~ cnidscheme:dbd options:usedots,invisibledots,upriv perm:0770
    /folder "TimeMachine" allow:user cnidscheme:dbd options:tm
    su
    /etc/init.d/netatalk stop
    /etc/init.d/netatalk start

  • [Solved] Vuurmuur not loading

    Hello,  I am having problems starting up vuurmuur in Arch, I am not sure but I think I did all that I was supose to do but still the dam daemon doesn't start up.
    I have installed vuurmuur from the AUR and added vuurmuur and iptables as daemons in rc.conf as instructed, I am having fault status at boot cause of it but they don't show up in /var/log/everything.log or dmesg (how can one easylly see the boot log for faults?)
    Running vuurmuur_conf I can solve all the faults except for the daemons.
    Running vuurmuur-initd.sh start I get:
    [root@archbox scripts]# sh ./vuurmuur-initd.sh start
    Starting firewall: Vuurmuur:
        Loading modules:    ip_tables iptable_filter iptable_mangle iptable_nat ip_conntrack ipt_state ip_conntrack_ftp ip_nat_ftp ip_queue
        Loading Vuurmuur:    FAILED.
        Loading Vuurmuur_log:    FAILED.
    Starting firewall: Vuurmuur: done
    vuurmuur_conf still says that the daemons are down.
    Any ideas / help ?
    Last edited by brunopereira81 (2010-10-11 14:18:54)

    Loaded wrong scrip, got the wrong output.
    Correct script to load is  /etc/rc.d/rc.vuurmuur and errors log, including the ones that are show during boot, is located in /var/logs/vuurmuur/errors.log.
    After running /etc/rc.d/vuurmuur, looking and solving the problems at shown at the log all is up and running.

  • CS5 Playback Settings grayed out and no longer can set playback on external monitor.

    I like to view my projects while editing on an external monitor but the Playback Settings are grayed out. I've done all my prior projects with external monitor display enabled with no problems and can go back to a prior projects completed and view them using an external playback monitor.  For some reason, the Playback Settings on my latest project are grayed out and I'm not able to set Desktop Video Display During Playback.
    The last project worked on was about 3 months ago. Last week, I started working on two new projects and noticed that I wasn't able to set playback to my external monitor. All my devices are hooked up and I can review older projects on the external monitor but can't set two new projects to use display on the external monitor.  
    Anyone have any ideas?
    Problem solved. My fault.
    The Sequence Preset Settings selected must support the device the external monitor is connected to. In my case, IEEE 1394 firewire. I corrected the new project to the correct Sequence Settings and can now view playback on the external monitor.

    http://www.blackmagicdesign.com/press/pressdetails?releaseID=42319
    "The Desktop Video 9.7.5 software update allows users to take advantage of many new features in the Adobe Creative Cloud desktop applications such as powerful new editing timelines and shortcuts and audio mixing with Adobe Premiere Pro® CC and new creative and visual effects tools with Adobe After Effects® CC."
    So everything should be covered on that front. And as I listed, I was getting playback out of AE CC, so I feel it is solely an issue in Premiere. That was worth checking out though since CC is so new. Thanks for replying.

  • Mac OS X and Linux Zeroconf LAN irregularities

    Mac OS X and Linux Zeroconf LAN irregularities
    I would like to at least understand, if not remedy,
    an annoyance in establishing the connection between
    my Mac and my Linux box. I have yet to find anything
    constructive relative to the issue via the google
    shuffle or manual pages. Any thoughts, experiences
    and/or further troubleshooting steps would be
    appreciated. Thank you.
    ==============================================
    Installation:
    PMac G5 running OS X Tiger (10.4.4)
    Linux printer is shared with Mac via CUPS,
    not classic AppleTalk.
    P4 with Debian Etch (testing), kernel 2.6.12-1-686,
    Gnome desktop and USB attached printer and scanner.
    With netatalk 2.0.3-4 and task-howl (0.9.5-2), which
    includes the howl mdnsresponder (0.9.5-2), installed.
    Only the netatalk afpd and cnid_metad deamons are
    being run.
    hardwired ethernet with the Mac and Linux box connected
    to a Belkin 4 port router
    ==============================================
    Trials:
    If I boot up both my Mac and Linux box:
    Linux has autoipd, mDNSResponder and nifd daemons running.
    Mac has mDNSResponder and netinfod daemons running (don't
    know which others are pertinent to note).
    If on my Mac in a Finder pane I click Network -> My Network
    -> debian1 -> Connect then I get the message:
    AFP connection status
    Looking up "debian1.local.."
    which times out with the message:
    Connection failed - server may not exist blah blah
    In can however, on my Mac in the Finder menu bar select
    Go -> Connect to Server -> enter afp://192.168.2.48/
    (my Linux box) -> enter user and password of shared
    directory -> select share to mount; and I have my
    connection. If I dismount the share though, within a
    session, and try to connect again this method works and
    the Finder pane method still does not.
    Alternatively, on my Linux box I can run the cli
    # /etc/init.d/mdnsresponder restart
    Then back on my Mac the Finder pane method of establishing
    a connection (that failed above) works as it should.
    Further, I can dismount the share and reconnect with this
    method any number of times in the same session, and even
    reconnect with this method after rebooting only my Mac.
    However, if I reboot my Linux box I'm back to Finder menu
    bar or mdnsresponder restart reconnect choices.
    ==============================================
    What the above trials tell me is that if I restart
    mdnsreaponder then everything is "peachy" until my Linux
    box is rebooted. What they do not tell me is if there is
    something flakey with mdnsresponder, my Linux installation,
    an incompatibility with Tiger, or even some other
    interference on either box.
    ==============================================
    Lee C
    "Life is judged with all the blindness of life itself."
    -- George Santayana
    (see Backup::Restore article
    http://homepage.mac.com/lee_cullens/Bx3.html )
    (see Artworks sampling
    http://homepage.mac.com/lee_cullens/Artworks.pdf )

    I posted the following to the Debian list for obvious reasons, but I'm also posting it here in the hope that someone might shed some light on my suspicions relative to the Mac log.
    The howl-tools portion of my zeroconf installation is being phased
    out in favor of the newer Avahi as I understand it. However, Avahi
    hasn't made its way down to testing yet so for the time being I'm
    trying to make do with howl-tools. The point in my mentioning
    this here is that much of the information I find is outdated.
    That said, the only thing I've found in the Linux bootup logs yet
    (using dmesg) that I recognize is the line
    autoipd uses obsolete (PFINET,SOCKPACKET)
    So, using autoipd as a starting point for further researching
    this issue I found the following
    (at http://www.porchdogsoft.com/products/howl/InstallUnix.html )
    Ideally, autoipd should run only in the event that the interface has not been statically configured and DHCP fails. Running autoipd this way requires modification to the standard distribution boot scripts for your OS. These modifications vary depending on your version of Linux or FreeBSD. On RedHat Linux, for example, the /sbin/ifup script may be modified to launch autoipd in the event that dhclient fails. On our systems, we added the following line to /sbin/ifup right after dhclient is launched so that autoipd runs whenever DHCP fails:
    elif [ -z "`pidof -x dhclient`" ] && [ -z "`pidof -x dhcpcd`" ] && [ -z "`pidof -x pump`" ] && [ -x /usr/local/bin/autopid ] && /usr/local/bin/autoipd -i ${DEVICE}; then echo $"started autoip."
    Note that since this change causes "$NUMDEFROUTES" to become zero-length, the subsequent code in /sbin/ifup for fixing the duplicate routes generated by DHCP also gets modified in the howl version of ifup.
    You may need to modify your boot scripts differently depending on your platform. We have included the original ifup script for RedHat 9 along with our modified version (howl_ifup) as an example so that you may more easily identify how to modify the boot scripts for your platform.
    A lot of Greek to me but I did look in /etc/init.d and found
    the autoipd script which is the normal boilerplate (same as all
    the others with autoipd substituted for the daemon name).
    Even if I felt comfortable adding the above in the
    /etc/init.d/autoipd script, I have no idea whether it would be
    dealt with after dhclient.
    I also found in the Mac system log after a reboot:
    Jan 26 02:22:48 slpmacg5 mDNSResponder: Adding browse domain local.
    Jan 26 02:22:48 slpmacg5 configd[33]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
    Jan 26 02:22:48 slpmacg5 configd[33]: posting notification com.apple.system.config.network_change
    Jan 26 02:22:48 slpmacg5 lookupd[80]: lookupd (version 369.2) starting - Thu Jan 26 02:22:48 2006
    Jan 26 02:22:49 slpmacg5 configd[33]: target=enable-network: disabled
    Jan 26 02:22:50 slpmacg5 configd[33]: AppleTalk startup complete
    Jan 26 02:23:59 slpmacg5 automount[148]: NSLXResolveDNS will try and resolve [debian1] of type [afpovertcp.tcp.] in location [local.]\n
    so I'm thinking (dangerous at my age) that my Mac isn't "discovering"
    what it needs until I restart (stop and start) mdnsresponder on my Linux box????
    What I'm asking is whether anyone thinks this (autoipd) on Linux is a
    likely cause of my described connection annoyance?
    If so, is the referenced info applicable to Debian today and how
    would one go about applying it?
    Or alternately if so, might it make sense to just disable autoipd
    startup altogether and how would I best go about that - just something
    like update-rc.d autoipd remove????????
    Thank you,
    Lee C

Maybe you are looking for