SixXS::Sunset 2017-06-06

Aiccu on Mac OS X - exited with exit code: 2
[de] Carmen Sandiego on Sunday, 10 January 2010 00:07:54
Hi, i installed aiccu yesterday. My AYIYA tunnel works. I found that my console log is filling up with lines like: 09.01.10 23:58:26 org.macports.aiccu[1297] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 09.01.10 23:58:56 com.apple.launchd[1] (org.macports.aiccu[1297]) Exited with exit code: 2 09.01.10 23:58:56 org.macports.aiccu[1304] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 09.01.10 23:59:26 com.apple.launchd[1] (org.macports.aiccu[1304]) Exited with exit code: 2 09.01.10 23:59:27 org.macports.aiccu[1318] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 09.01.10 23:59:57 com.apple.launchd[1] (org.macports.aiccu[1318]) Exited with exit code: 2 09.01.10 23:59:57 org.macports.aiccu[1329] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 10.01.10 00:00:27 com.apple.launchd[1] (org.macports.aiccu[1329]) Exited with exit code: 2 10.01.10 00:00:27 org.macports.aiccu[1336] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 10.01.10 00:00:57 com.apple.launchd[1] (org.macports.aiccu[1336]) Exited with exit code: 2 10.01.10 00:00:57 org.macports.aiccu[1342] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 10.01.10 00:01:28 com.apple.launchd[1] (org.macports.aiccu[1342]) Exited with exit code: 2 10.01.10 00:01:28 org.macports.aiccu[1346] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 10.01.10 00:01:58 com.apple.launchd[1] (org.macports.aiccu[1346]) Exited with exit code: 2 10.01.10 00:01:58 org.macports.aiccu[1350] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) 10.01.10 00:02:28 com.apple.launchd[1] (org.macports.aiccu[1350]) Exited with exit code: 2 10.01.10 00:02:28 org.macports.aiccu[1355] 127 0 0x34577000 0x7000 0x6000 foo.tun (1.0) But while this I am still able to ping my tunnel end point, so the tunnel works. Is this normal behavior? How can I fix this? I am on a iMac G5, wunning Leopard. Greetings and THANKS! Christoph
Aiccu on Mac OS X - exited with exit code: 2
[ch] Jeroen Massar SixXS Staff on Sunday, 10 January 2010 02:54:54
That version is broken, see aiccu - daemondo automatically restarts it, the reason why it exists is because something is broken..... It doesn't seem the macports people really care about their modifications causing ddos attempts on our TIC servers though....
Aiccu on Mac OS X - exited with exit code: 2
[de] Carmen Sandiego on Sunday, 10 January 2010 13:10:07
So you suggest to uninstall the macports version? I think it succs that maintainers in macports very often do not care for their ports...
Aiccu on Mac OS X - exited with exit code: 2
[de] Carmen Sandiego on Sunday, 10 January 2010 13:41:06
OK. I deinstalled the macports tuntaposx and aiccu. Then I used the tuntaposx installer, then I built aiccu with the guidance from the wiki. I found out from the wiki, that "daemonize" should be set to false. During my macports-phase, this was set to true. Maybe that was why the aiccu kept crashing? Anyone knows? I am not very familiar with the launchd stuff. Maybe the macports version was not the problem - but the problem sat infront of the imac:-) Now it runs like a charme anyways...

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker