memory_limit error

rhubarb
Posts: 54
Joined: Wed May 05, 2010 1:59 pm

memory_limit error

Postby rhubarb » Mon Mar 19, 2012 1:49 pm

Hi
A while back I started getting a greyhole problem. I noticed it because my storage pool disks never went idle (as they should after X minutes of inactivity).

Below is an extract from greyhole.log. I first noticed the memory_limit error. I have tried increasing this value but it has not helped. I now aslo see that the daemon is restarting. Not sure what to make of this. (The PHP warning may not be significant, but it would be nice to fix that too)

tail -f /var/log/greyhole.log
Mar 19 21:39:10 6 daemon: Greyhole (version 0.9.20) daemon started.
Mar 19 21:39:10 7 daemon: Loading metadata store backup directories...
Mar 19 21:39:10 7 daemon: Found 2 directories in the settings table.
Mar 19 21:39:10 4 parse_logs: PHP Warning [8]: Trying to get property of non-object in /usr/bin/greyhole on line 3896; BT: greyhole[L2508] parse_samba_spool() => greyhole[L4045] parse_samba_log(1)
Mar 19 21:39:10 7 parse_logs: Parsing Samba logs...
Mar 19 21:39:10 7 parse_logs: Done parsing.
Mar 19 21:39:11 7 simplify_tasks: Simplifying pending tasks.
Mar 19 21:39:11 4 parse_logs: PHP Warning [8]: Trying to get property of non-object in /usr/bin/greyhole on line 3896; BT: greyhole[L2511] parse_samba_spool() => greyhole[L4045] parse_samba_log(1)
Mar 19 21:39:11 7 parse_logs: Parsing Samba logs...
Mar 19 21:39:11 7 parse_logs: Done parsing.
Mar 19 21:39:11 6 rename: Now working on task ID 314696: rename flip/120228_1 -> flip/120228
Mar 19 21:39:11 6 rename: Directory renamed: /mnt/500GB_1/lz/flip/120228_1 -> /mnt/500GB_1/lz/flip/120228
Mar 19 21:39:11 7 rename: Loading metadata files for (dir) flip/120228 ...
Mar 19 21:39:11 7 rename: Loading metafiles for flip/120228/VID00064.MP4 ...
Mar 19 21:39:11 7 rename: Got 2 metadata files.
Mar 19 21:39:11 2 rename: 617510737510% memory usage, exiting. Please increase memory_limit in /etc/greyhole.conf


[root@fedora-arm ~]# uname -r; rpm -q samba hda-greyhole
2.6.35.4
samba-3.4.7-58.fc12.armv5tel
hda-greyhole-0.9.20-1.armv5tel

fpaste /etc/samba/smb.conf; fpaste /etc/greyhole.conf
Uploading (4.3K)...
http://fpaste.org/Au0x/
Uploading (1.3K)...
http://fpaste.org/Zz7U/

mount; fdisk -l; df -h; greyhole --stats
/dev/root on / type nfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdd1 on /mnt/500GB_1 type ext4 (rw,nosuid,nodev)
/dev/sdc1 on /mnt/500GB_2 type ext4 (rw,nosuid,nodev)

Disk /dev/sda: 1967 MB, 1967128576 bytes
62 heads, 61 sectors/track, 1015 cylinders
Units = cylinders of 3782 * 512 = 1936384 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 1016 1920993+ 6 FAT16
Partition 1 has different physical/logical endings:
phys=(54, 61, 61) logical=(1015, 54, 24)
/dev/sda2 56 1021 1826706 83 Linux

Disk /dev/sdb: 7948 MB, 7948206080 bytes
245 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 15190 * 512 = 7777280 bytes
Disk identifier: 0x0001ba78

Device Boot Start End Blocks Id System
/dev/sdb1 1 203 1536000 6 FAT16
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 32, 33) logical=(0, 33, 3)
Partition 1 has different physical/logical endings:
phys=(191, 89, 26) logical=(202, 91, 26)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 203 877 5120000 83 Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(191, 89, 27) logical=(202, 91, 27)
Partition 2 has different physical/logical endings:
phys=(828, 194, 6) logical=(876, 122, 44)
Partition 2 does not end on cylinder boundary.
/dev/sdb3 877 1022 1104896 82 Linux swap / Solaris
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(828, 194, 7) logical=(876, 122, 45)
Partition 3 has different physical/logical endings:
phys=(966, 80, 10) logical=(1021, 239, 32)
Partition 3 does not end on cylinder boundary.

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000de67b

Device Boot Start End Blocks Id System
/dev/sdc1 1 60801 488384001 8e Linux LVM

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000bdbae

Device Boot Start End Blocks Id System
/dev/sdd1 1 60801 488384001 8e Linux LVM
Filesystem Size Used Avail Use% Mounted on
/dev/root 4.9G 2.5G 2.2G 53% /
tmpfs 251M 240K 251M 1% /dev/shm
/dev/sdd1 459G 121G 315G 28% /mnt/500GB_1
/dev/sdc1 459G 146G 290G 34% /mnt/500GB_2

Greyhole Statistics
===================

Storage Pool
Total - Used = Free + Trash = Possible
/mnt/500GB_1/gh: 0G - 0G = 0G + 0G = 0G
/mnt/500GB_2/gh: 0G - 0G = 0G + 0G = 0G
==========================================
Total: 0G - 0G = 0G + 0G = 0G

[root@fedora-arm ~]#

NOTE I might be using SQLITE. not sure
[root@fedora-arm ~]# mysql -u root -phda -e "select * from disk_pool_partitions" hda_production
+----+--------------+--------------+---------------------+---------------------+
| id | path | minimum_free | created_at | updated_at |
+----+--------------+--------------+---------------------+---------------------+
| 1 | /mnt/500GB_1 | 10 | 2011-12-11 17:05:33 | 2011-12-11 17:05:33 |
| 2 | /mnt/500GB_2 | 10 | 2011-12-11 17:05:34 | 2011-12-11 17:05:34 |
+----+--------------+--------------+---------------------+---------------------+
[root@fedora-arm ~]#


[root@fedora-arm ~]# mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la | fpaste
Uploading (1.4K)...
http://fpaste.org/jQ0v/

User avatar
radioz
Posts: 406
Joined: Tue Nov 24, 2009 1:07 pm

Re: memory_limit error

Postby radioz » Mon Mar 19, 2012 9:01 pm

I'm not familiar with greyhole, but could that error be referring to system memory rather than disk space?

How much ram to you have?
Use the 'free' command to check.

rhubarb
Posts: 54
Joined: Wed May 05, 2010 1:59 pm

Re: memory_limit error

Postby rhubarb » Tue Mar 20, 2012 5:40 am

Hi
I think memory_limit refers to a PHP limit. This can be adjusted using a greyhole config. There is very little info on it and it is difficult to understand

Peter


[root@fedora-arm ~]# free
total used free shared buffers cached
Mem: 513668 377620 136048 0 172508 137564
-/+ buffers/cache: 67548 446120
Swap: 1104892 0 1104892

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: memory_limit error

Postby bigfoot65 » Tue Mar 20, 2012 6:00 am

Typically there is no need to increase PHP memory. I have not heard of any case with Greyhole where that was required.

Did you check the size of your log file? I have seen that grow quite large and might cause problems.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

rhubarb
Posts: 54
Joined: Wed May 05, 2010 1:59 pm

Re: memory_limit error

Postby rhubarb » Tue Mar 20, 2012 6:44 am

Hi


[root@fedora-arm ~]# ls -al /var/log/greyhole*
-rw-r--r-- 1 root root 890431 Mar 20 14:42 /var/log/greyhole.log
-rw-r--r-- 1 root root 89091 Mar 4 03:38 /var/log/greyhole.log-20120304.gz
-rw-r--r-- 1 root root 84424 Mar 5 03:18 /var/log/greyhole.log-20120305.gz
-rw-r--r-- 1 root root 88917 Mar 6 04:09 /var/log/greyhole.log-20120306.gz
-rw-r--r-- 1 root root 84359 Mar 7 03:31 /var/log/greyhole.log-20120307.gz
-rw-r--r-- 1 root root 86867 Mar 8 03:33 /var/log/greyhole.log-20120308.gz
-rw-r--r-- 1 root root 63851 Mar 19 15:10 /var/log/greyhole.log-20120319.gz
-rw-r--r-- 1 root root 45044 Mar 20 03:45 /var/log/greyhole.log-20120320.gz

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: memory_limit error

Postby bigfoot65 » Tue Mar 20, 2012 7:38 am

All looks fine with the log files. Is this a plug computer? If so, there is obviously a limit on memory available. Not sure if you will have enough left to increase the limit in the greyhole.conf file.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

rhubarb
Posts: 54
Joined: Wed May 05, 2010 1:59 pm

Re: memory_limit error

Postby rhubarb » Tue Mar 20, 2012 9:26 am

Hi
Yes, this is a dreamplug

I increased memory_limit to 180M (128M default I think) .

vi /var/hda/platform/html/config/greyhole.yml
memory_limit: 180M

and also hacked the greyhole config since I didnt know how to update it automatically from Amahi config
vi /etc/greyhole.conf
memory_limit = 180M

I hope I got the syntax differences right

restarted the plug, but it doesnt seem to have fixed the problem.

Peter

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: memory_limit error

Postby bigfoot65 » Tue Mar 20, 2012 10:01 am

You may have reached the limits of the plug. I have not heard much feedback from users in respect to the plug and Greyhole. Since this is Fedora 12, there are no new updates coming from Fedora or Amahi.

We have not had a new ARM release since this one. I am unsure how to tell you to proceed. Maybe post in the Plug topic area as there are a few who still use these devices.

Have you checked the Greyhole web site for help on this error? Also, might be good to contact the author directly to see if he can be of assistance.

Sorry I cannot help more.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

rhubarb
Posts: 54
Joined: Wed May 05, 2010 1:59 pm

Re: memory_limit error

Postby rhubarb » Wed Mar 21, 2012 2:51 pm

Hi

It looks like the memory_limit calculation is giving spurious results (eg not a percentage):-

Mar 19 21:39:11 2 rename: 617510737510% memory usage, exiting. Please increase memory_limit in /etc/greyhole.conf

So I hacked the greyhole PHP script

vi /usr/bin/greyhole

and disabled the exit that would normally happen over 95%

//gh_log(CRITICAL, $used . '% memory usage, exiting. Please increase memory_limit in /etc/greyhole.conf');
gh_log(DEBUG, $used . '% memory usage, exiting. Please increase memory_limit in /etc/greyhole.conf');

and things seem to be running OK again (touch wood)

Peter

User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: memory_limit error

Postby bigfoot65 » Wed Mar 21, 2012 3:09 pm

Awesome. I hope it keeps going for you. Sounds like you are on the edge.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2

Who is online

Users browsing this forum: No registered users and 52 guests