Problems with logs getting full in Pogoplug Model P21

by **eljohnsmith** » Mon Jun 20, 2011 9:17 pm

I installed the Arch Linux ARM using the instructions in the wiki for PogoPlug Pro. Everything seems to be working as needed except for 2 things. First one is the commands sync, sync, reboot hang the system and it has to be restarted manually.

Second one is the real problem, my logs get full because of an error similar to the one described here: viewtopic.php?f=9&t=1214&p=6786&hilit=unable+to+receive+ctrl+connection%3A+Function+not+implemented#p6786

The logs keep recording

Code: Select all: alarm udevd[377]: unable to receive ctrl connection: Function not implemented

I tried the fix suggested on that thread and I receive a message telling me that the udev-compat package is corrupted. Can someone help with that. The output is shown below.

Thanks,

Code: Select all: # pacman -Sy udev-compat :: Synchronizing package databases... core 0.0K 0.0K/s 00:00:00 [----------------------] 0%error: error writing to file '/var/lib/pacman/sync/core.db.part': No space left on device error: failed to update core (failed to retrieve some files) extra 0.0K 0.0K/s 00:00:00 [----------------------] 0%error: error writing to file '/var/lib/pacman/sync/extra.db.part': No space left on device error: failed to update extra (failed to retrieve some files) community is up to date aur is up to date resolving dependencies... looking for inter-conflicts... Targets (1): udev-compat-171-2 Total Download Size: 0.00 MB Total Installed Size: 0.02 MB Proceed with installation? [Y/n] y :: Retrieving packages from core... udev-compat-171-2-arm 0.0K 0.0K/s 00:00:00 [----------------------] 0% udev-compat-171-2-arm 0.9K 1678.5K/s 00:00:00 [######################] 100% (0/1) checking package integrity [----------------------] 0%:: File udev-compat-171-2-arm.pkg.tar.xz is corrupted. Do you want to delete it? [Y/n] y (1/1) checking package integrity [######################] 100% error: failed to commit transaction (invalid or corrupted package) udev-compat-171-2-arm.pkg.tar.xz is invalid or corrupted Errors occurred, no packages were upgraded.

by **eljohnsmith** » Mon Jun 20, 2011 9:37 pm

Update: I was able to install udev-compat after a second try but the logs keep getting full with the error. Here is the install log for udev-compat now:

Code: Select all: # pacman -Sy udev-compat :: Synchronizing package databases... core 0.0K 0.0K/s 00:00:00 [----------------------] 0% core 36.3K 183.6K/s 00:00:00 [######################] 100% extra 0.0K 0.0K/s 00:00:00 [----------------------] 0% extra 80.0K 101.1K/s 00:00:03 [####------------------] 19% extra 176.0K 167.4K/s 00:00:01 [#########-------------] 43% extra 240.0K 193.3K/s 00:00:00 [############----------] 59% extra 256.0K 155.2K/s 00:00:00 [#############---------] 63% extra 288.0K 139.3K/s 00:00:00 [###############-------] 70% extra 336.0K 141.4K/s 00:00:00 [##################----] 82% extra 368.0K 131.1K/s 00:00:00 [###################---] 90% extra 406.0K 185.7K/s 00:00:02 [######################] 100% community is up to date aur is up to date resolving dependencies... looking for inter-conflicts... Targets (1): udev-compat-171-2 Total Download Size: 0.00 MB Total Installed Size: 0.02 MB Proceed with installation? [Y/n] y :: Retrieving packages from core... udev-compat-171-2-arm 0.0K 0.0K/s 00:00:00 [----------------------] 0% udev-compat-171-2-arm 0.9K 1872.3K/s 00:00:00 [######################] 100% (0/1) checking package integrity [----------------------] 0%(1/1) checking package integrity [######################] 100% (0/1) checking for file conflicts [----------------------] 0%(1/1) checking for file conflicts [######################] 100% (1/1) installing udev-compat [----------------------] 0%(1/1) installing udev-compat [######################] 100%

Here is the tail of my errors.log file which is identical to everything.log and daemon.log :

Code: Select all: [root@alarm log]# tail errors.log Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented [root@alarm log]# tail everythingl.log Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm syslog-ng[1307]: syslog-ng shutting down; version='3.2.4' [root@alarm log]# tail daemon.log Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented Jun 20 14:34:20 alarm udevd[377]: unable to receive ctrl connection: Function not implemented [root@alarm log]# exit

by **WarheadsSE** » Mon Jun 20, 2011 9:37 pm

Follow the fix for udev, then pacman -Scc pacman -Syyuf

by **eljohnsmith** » Mon Jun 20, 2011 9:48 pm

WarheadsSE wrote:Follow the fix for udev, then pacman -Scc pacman -Syyuf

Thanks for your answer, and I would like to take this time to publicly thank you for all the information that you have posted. I have read a lot of your posts while configuring this device and they have helped me a great deal.

I tried the commands you suggested and I still have the same problem. As soon as I turn syslog-ng on it starts logging the same error over and over again.

Here is the log of the installation steps I performed:

Code: Select all: pacman -Sy udev-compat :: Synchronizing package databases... core is up to date extra 0.0K 0.0K/s 00:00:00 [----------------------] 0% extra 32.0K 48.1K/s 00:00:07 [#---------------------] 7% extra 112.0K 145.4K/s 00:00:02 [#####-----------------] 27% extra 224.0K 263.0K/s 00:00:00 [############----------] 55% extra 400.0K 415.3K/s 00:00:00 [#####################-] 98% extra 405.9K 437.8K/s 00:00:01 [######################] 100% community is up to date aur is up to date warning: udev-compat-171-2 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... Targets (1): udev-compat-171-2 Total Download Size: 0.00 MB Total Installed Size: 0.02 MB Proceed with installation? [Y/n] y (0/1) checking package integrity [----------------------] 0%(1/1) checking package integrity [######################] 100% (0/1) checking for file conflicts [----------------------] 0%(1/1) checking for file conflicts [######################] 100% (1/1) upgrading udev-compat [----------------------] 0%(1/1) upgrading udev-compat [######################] 100% [root@alarm ~]# pacman -Scc Cache directory: /var/cache/pacman/pkg/ Do you want to remove ALL files from cache? [y/N] y removing all files from cache... Database directory: /var/lib/pacman/ Do you want to remove unused repositories? [Y/n] y Database directory cleaned up [root@alarm ~]# pacman -Syyuf :: Synchronizing package databases... core 0.0K 0.0K/s 00:00:00 [----------------------] 0% core 32.0K 43.8K/s 00:00:00 [###################---] 88% core 36.3K 148.5K/s 00:00:00 [######################] 100% extra 0.0K 0.0K/s 00:00:00 [----------------------] 0% extra 80.0K 101.1K/s 00:00:03 [####------------------] 19% extra 192.0K 220.8K/s 00:00:00 [##########------------] 47% extra 336.0K 371.9K/s 00:00:00 [##################----] 82% extra 405.9K 511.1K/s 00:00:01 [######################] 100% community 0.0K 0.0K/s 00:00:00 [----------------------] 0% community 128.0K 163.3K/s 00:00:01 [#######---------------] 33% community 272.0K 315.7K/s 00:00:00 [###############-------] 71% community 378.7K 632.0K/s 00:00:01 [######################] 100% aur 0.0K 0.0K/s 00:00:00 [----------------------] 0% aur 9.1K 4.4M/s 00:00:00 [######################] 100% :: Starting full system upgrade... warning: diffutils: local (3.0-3) is newer than core (3.0-2) warning: sysfsutils: local (2.1.0-7) is newer than core (2.1.0-6) warning: tcp_wrappers: local (7.6-13) is newer than core (7.6-12) resolving dependencies... looking for inter-conflicts... Targets (1): cronie-1.4.7-9 Total Download Size: 0.05 MB Total Installed Size: 0.25 MB Proceed with installation? [Y/n] y :: Retrieving packages from core... cronie-1.4.7-9-arm 0.0K 0.0K/s 00:00:00 [----------------------] 0% cronie-1.4.7-9-arm 32.0K 48.2K/s 00:00:00 [#############---------] 63% cronie-1.4.7-9-arm 50.7K 168.4K/s 00:00:00 [######################] 100% (0/1) checking package integrity [----------------------] 0%(1/1) checking package integrity [######################] 100% (1/1) upgrading cronie

by **slycat** » Tue Jun 21, 2011 6:50 pm

the best thing I can tell you is what the lot of us with the same problem have been doing.

Code: Select all: ##in rc.conf blacklist syslog-ng by adding a ! like so MODULES = (blah blah blah !syslog-ng blah) ##However this stops ALL auto logging

Code: Select all: ##in /etc/rc.local add kill $(pidof udevd) sleep3 udevd &

Code: Select all: ##If you need nothing more of your logs cd /var/log rm errors.log daemons.log everything.log touch errors.log daemons.log everything.log

by **fnu** » Fri Sep 02, 2011 4:13 pm

@slycat

Faced the same problem, filling my disk space infinitely ny log files and syslog-ng hooks alway with 100% on one core of my PP.

It seems like a stupid timing problem, since killing and restarting udevd does work. After that log sizes stays moderate and e.g. usb disks are realized by system ... unfortunately not my usb card reader, but this is a different story ...

Regards
fnu

by **WarheadsSE** » Fri Sep 02, 2011 4:18 pm

This problem was fixed, as noted in a sticky.

please
pacman -Syu udev-oxnas

by **fnu** » Sat Sep 03, 2011 6:14 pm

@WarheadSE

Ok, but before going into details, I want to clarify your comment, looking to the post here: http://archlinuxarm.org/forum/viewtopic.php?p=8812&f=29#p8812?

And I did follow your hint:

Code: Select all: pacman -Syu udev-oxnas :: Synchronizing package databases... core is up to date extra is up to date community is up to date aur is up to date :: Starting full system upgrade... warning: sysfsutils: local (2.1.0-7) is newer than core (2.1.0-6) warning: tcp_wrappers: local (7.6-13) is newer than core (7.6-12) resolving dependencies... looking for inter-conflicts... :: udev-oxnas and udev are in conflict. Remove udev? [y/N] y Remove (1): udev-173-3 Total Removed Size: 1.77 MB Targets (1): udev-oxnas-171-2 Total Download Size: 0.00 MB Total Installed Size: 1.74 MB Proceed with installation? [Y/n] (1/1) checking package integrity [#################################################] 100% (1/1) checking for file conflicts [#################################################] 100% error: failed to commit transaction (conflicting files) udev-oxnas: /lib/udev/devices/console exists in filesystem udev-oxnas: /lib/udev/devices/core exists in filesystem udev-oxnas: /lib/udev/devices/fd exists in filesystem udev-oxnas: /lib/udev/devices/fuse exists in filesystem udev-oxnas: /lib/udev/devices/kmsg exists in filesystem udev-oxnas: /lib/udev/devices/net/tun exists in filesystem udev-oxnas: /lib/udev/devices/null exists in filesystem udev-oxnas: /lib/udev/devices/ppp exists in filesystem udev-oxnas: /lib/udev/devices/stderr exists in filesystem udev-oxnas: /lib/udev/devices/stdin exists in filesystem udev-oxnas: /lib/udev/devices/stdout exists in filesystem udev-oxnas: /lib/udev/devices/zero exists in filesystem Errors occurred, no packages were upgraded.

Since I'd expect a version 173-3 should be installed, whereas I only can query a version 171-2:

Code: Select all: pacman -Si udev-oxnas Repository : core Name : udev-oxnas Version : 171-2 URL : http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html Licenses : GPL Groups : base Provides : udev=171 Depends On : glibc coreutils util-linux libusb-compat glib2 module-init-tools>=3.11 pciutils Optional Deps : None Conflicts With : pcmcia-cs hotplug initscripts<2009.07 udev Replaces : devfsd Download Size : 187.06 K Installed Size : 1780.00 K Packager : Kevin Mihelich <kevin@Arch Linux ARM.com> Architecture : arm Build Date : Thu 11 Aug 2011 04:55:30 AM CEST MD5 Sum : c41e28df5d903cf26e7a1381ea4c861f Description : The userspace dev tools (udev-oxnas)

And a look into repo's directory here http://archlinuxarm.org/arm/index.php?d=core/, does confirm this.

Regards
fnu

by **fnu** » Sun Sep 04, 2011 10:36 am

Ok, for all of you might being run into same issue after installation. You need to uninstall original udev due ignoring all dependencies, needed some time to went into pacman as apt/dpkg user ...

Code: Select all: #\> sudo pacman -Rddn udev #\> sudo pacman -Syu udev-oxnas => In case everything did run fine, change back you're workaround in /etc/rc.local and do #\> sudo reboot

Do these steps right behind another, don't do anything else in between. You're system could become unusable and you might be start over with a fresh installation ...

Regards
fnu

Problems with logs getting full in Pogoplug Model P21

Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Re: Problems with logs getting full in Pogoplug Model P21

Who is online