[Solved] OTRS v4 Appliance PostgreSQL Crash

[netjess]

Hello,

My OTRS vAppliance has crashed. I get the following error:
konnte temporre Statistikdatei >>pg_stat_tmp/pgstat.tmp<< nicht schreiben: Auf dem Gert ist kein Speicherplatz mehr verf

Which running through Google translate returns:
could not write temporre statistics file >> pg_stat_tmp / pgstat.tmp << : on the device is no more space feature

Here is the output of "df -h":
root@otrs:~# df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 2.0G 0 2.0G 0% /TARGET/RAM/lib/init/rw
udev 10M 96K 10M 1% /dev
tmpfs 2.0G 4.0K 2.0G 1% /dev/shm
tmpfs 1.0G 192K 1.0G 1% /SOURCE/RAMDISK
/dev/sda1 3.8G 375M 3.3G 11% /SYSTEM
/dev/vg/SHARE 4.2G 4.0G 0 100% /SOURCE/SHARE
/dev/vg/BACKUP 6.9G 2.7G 3.9G 42% /BACKUP
/dev/vg/NODE 1.4G 35M 1.3G 3% /SOURCE/NODE
/dev/loop0 254M 254M 0 100% /SOURCE/FIRMWARE
/dev/loop1 356K 356K 0 100% /SOURCE/LINKS
unionfs 1.0G 192K 1.0G 1% /TARGET/RAM
unionfs 1.4G 35M 1.3G 3% /TARGET/NODE
unionfs 4.2G 4.0G 0 100% /TARGET/SHARE
#####################################################

I am not sure where this unionfs that appears full is generated or how I can increase it or clean it.
I boot to partition magic and it shows that the drive is 20GB but somehow that is not reflected in this.

Any ideas?

Thanks.

[crythias]

Code: Select all

/dev/vg/SHARE 4.2G 4.0G 0 100% /SOURCE/SHARE

[netjess]

crythias,
Thank you for your reply.
I saw that but I cannot find how to properly extend this partition.

Do you happen to know how or who I would contact? any information I have been able to find on enlarging this partion does not seem to match guides on the issue.
It is an LVM.
It seemed successful when I issued:
lvextend -l+100%FREE /dev/vg/SHARE
but when I try to resize the file system it doesn't find it.
##########################################################
root@otrs:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
BACKUP vg -wi-ao 7.00g
NODE vg -wi-ao 1.40g
SHARE vg -wi-ao 6.34g

root@otrs:~# lvdisplay
/dev/mapper/vg-NODE: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/vg/NODE
VG Name vg
LV UUID pJIPIu-nit9-gWxT-Uz7s-qjud-FKQZ-uZxTvK
LV Write Access read/write
LV Status NOT available
LV Size 1.40 GiB
Current LE 359
Segments 1
Allocation inherit
Read ahead sectors auto

/dev/mapper/vg-SHARE: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/vg/SHARE
VG Name vg
LV UUID B9ctop-N8PW-Pzc3-b1MV-ozLW-T1Hg-An5GVz
LV Write Access read/write
LV Status NOT available
LV Size 6.34 GiB
Current LE 1623
Segments 2
Allocation inherit
Read ahead sectors auto

/dev/mapper/vg-BACKUP: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/vg/BACKUP
VG Name vg
LV UUID HpB9fy-atPC-8c2l-Dnil-YrCw-jRAv-B0nw79
LV Write Access read/write
LV Status NOT available
LV Size 7.00 GiB
Current LE 1792
Segments 1
Allocation inherit
Read ahead sectors auto

root@otrs:~# ls /dev/vg
ls: cannot access /dev/vg: No such file or directory
####################################################################

It doesn't make sense. Hos does it boot if none of the paths exist?

[crythias]

Generally you manage ls versus mount point /SOURCE/SHARE. I don't think you can versus the /dev side.
beyond this, I can't give you much assistance except to move off appliance.

[wurzel]

Hi,

Appliance is a blackbox and you might want to ask the vendor for support? (otrs.com)
I would try to get the dump from the database and restore it on a clean linux.

Flo

[netjess]

Well thanks to a post at http://unix.stackexchange.com/questions ... er-missing

root@otrs:/# vgscan --mknodes
Reading all physical volumes. This may take a while...
Found volume group "vg" using metadata type lvm2
The link /dev/vg/NODE should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg/SHARE should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg/BACKUP should had been created by udev but it was not found. Falling back to direct link creation.

Then
root@otrs:/# resize2fs /dev/vg/SHARE
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/vg/SHARE is mounted on /SOURCE/SHARE; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 1
Performing an on-line resize of /dev/vg/SHARE to 1661952 (4k) blocks.
The filesystem on /dev/vg/SHARE is now 1661952 blocks long.


I now have extra space and a bit more time to work on getting off appliance and moved to a full build.
Our OTRS has become too important to risk to the hurdles of working with the appliance.

Thank you.