[X] My Assistant

Yeah I just restarted the server and then started the Client.

By the way what have i to do to get the bounty in Gs Sig? (IMG:[invalid] style_emoticons/default/laugh.gif)

PM sent

This post has been edited by G Just G: Jan 13 2013, 11:13

Got some new VPS recently but found one of them always got stopped itself when running, or even during startup:



The stop is random, could happen any time when the process is running, cannot be killed normally and need to "kill -9". But it is still accessible through SSH. Any suggestion for diagnostics besides contacting support?

This post has been edited by mnching: Jan 18 2013, 13:15

ＴＨＸ　　 (IMG:[invalid] style_emoticons/default/biggrin.gif)

Got some new VPS recently but found one of them always got stopped itself when running, or even during startup:



The stop is random, could happen any time when the process is running, cannot be killed normally and need to "kill -9". But it is still accessible through SSH. Any suggestion for diagnostics besides contacting support?

That image doesn't show anything other than ordinary info from H@H client.

That image doesn't show anything other than ordinary info from H@H client.

I believe that StonyCat had an issue with a OpenVZ VPS here: https://forums.e-hentai.org/index.php?showtopic=108730
and that that log comes from there.
I also believe that the problem went away (i.e. he got a better VPS) as StonyCat did try to shout for help anymore.

Hmpf Linux is made of trolling!

I had to restart a client but that fucker would not let me restart it. Then I tried 20 Minutes later and the same command worked... no typo because I copypasted it.

Yup, the number of things that can go wrong in an OS combined with Murphy's law is very well syntetised as trolling, there's always something wrong on any computer (VAX and DEC excluded, not much happen on those). We, just need to live with it.

If the universe was built with the same strategy as computer technology a woodpecker would be as dangerous as an atomic bomb. (IMG:[invalid] style_emoticons/default/dry.gif)

1.How can I use the same command like nologging, or maxconnction on a client running in windos?

2.If I am having a bad trust level, what are the right directions to adjust the parameters?

--------------------------------------------------------
First problem solved


--------------------------------------------------------
Spent the whole morning setting the auto-start of H@H following this thread and the H@H FAQ but still fail.
Came up with my own script at last.
//////////////////////////////////
#/etc/init/hath.conf

start on runlevel [2345]
stop on runlevel [016]

respawn

script
cd /home/hath
sudo -u hath java -jar HentaiAtHome.jar --disable_logging --use_more_memory
end script
//////////////////////////////////

I would like to know if there are any advantages of using exec as suggested in page 8 over using sudo,

This post has been edited by wypower2: Apr 18 2013, 08:22

1.How can I use the same command like nologging, or maxconnction on a client running in windos?

2.If I am having a bad trust level, what are the right directions to adjust the parameters?

--------------------------------------------------------
First problem solved
--------------------------------------------------------
Spent the whole morning setting the auto-start of H@H following this thread and the H@H FAQ but still fail.
Came up with my own script at last.
//////////////////////////////////
#/etc/init/hath.conf

start on runlevel [2345]
stop on runlevel [016]

respawn

script
cd /home/hath
sudo -u hath java -jar HentaiAtHome.jar --disable_logging --use_more_memory
end script
//////////////////////////////////

I would like to know if there are any advantages of using exec as suggested in page 8 over using sudo,

It's pretty obvious, exec (execute the software with the current user permission), sudo (executes the software with whatever user permission you wish for that specific command).
And if course readability.
From what I've gather when it comes to Trust, it's when something bad has happen between you and the H@H server, network wise (bad packets, unreachable packets, etc).

This is the one I posted:

CODE

#/etc/init/hath.conf

# Sets when it shall startup and shutdown.
start on startup      # You will need to check these are still used
stop on shutdown     # ------------------------||---------------------------

# Will restart the client incase daemon is killed.
respawn
respawn limit 99 5

script

user=' the user you want to run H@H '

exec su ${user} -c "/usr/bin/java -jar /home/${user}/HentaiAtHome.jar --silentstart"
end script

# This is will only execute after you've started the script
post-start script

end script

This post has been edited by GanGun : Apr 21 2013, 22:25

what do I do against sum no scape left on device error message on my 3 IP Server?

CODE

2013-04-23T03:21:38Z [info]
2013-04-23T03:21:38Z [ERROR] {org.hath.base.HentaiAtHomeClient.dieWithError(Hent
aiAtHomeClient.java:271)} Critical Error: Failed to load the database.
java.io.IOException: No space left on device
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:318)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:135)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:220)
        at java.io.Writer.write(Writer.java:157)
        at org.hath.base.Out.log(Out.java:210)
        at org.hath.base.Out.log(Out.java:190)
        at org.hath.base.Out.access$300(Out.java:36)
        at org.hath.base.Out$OutPrintStream.println(Out.java:290)
        at org.hath.base.Out.error(Out.java:173)
        at org.hath.base.HentaiAtHomeClient.dieWithError(HentaiAtHomeClient.java
:271)
        at org.hath.base.CacheHandler.<init>(CacheHandler.java:108)
        at org.hath.base.HentaiAtHomeClient.run(HentaiAtHomeClient.java:112)
        at java.lang.Thread.run(Thread.java:722)
2013-04-23T03:21:38Z [info] Shutting down...
2013-04-23T03:21:38Z [info] Your business is appreciated
root@server88-208-193-162:/h/h1#

This post has been edited by Ichy: Apr 23 2013, 05:22

Either get more space or start deleting stuff

You can see your current disk usage with:

CODE

df -h /

This:

CODE

du -a <DIR> | sort -nr | head -10

will show you the 10 largest directories/files used by H@H (replace <DIR> with the directory you're using for H@H)

thanks. Looks like I set my max disc Space wrong and now im at 100% (IMG:[invalid] style_emoticons/default/laugh.gif)

The second line tells me : -bash: syntax error near unexpected token `|'

And another question. Im safe to delete random files out of the directory?

edit: it is running again! yay

This post has been edited by Ichy: Apr 23 2013, 15:35

Hey guys I got a extra HD for my Server!

I did: sudo fdisk -l
and got:

CODE

root@server88-208-193-162:~# sudo fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000df921

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      499711      248832   83  Linux
/dev/sda2          499712     8499199     3999744   82  Linux swap / Solaris
/dev/sda3         8501246   488396799   239947777    5  Extended
/dev/sda5         8501248   488396799   239947776   8e  Linux LVM

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x88110625

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   488392064   244195008+  83  Linux

Disk /dev/mapper/VolGroup00-LogVol00: 245.7 GB, 245702328320 bytes
255 heads, 63 sectors/track, 29871 cylinders, total 479887360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/VolGroup00-LogVol00 doesn't contain a valid partition table
root@server88-208-193-162:~#

there is some weirdo error but if i continue

CODE

root@server88-208-193-162:~# sudo fdisk /dev/sdb

Command (m for help): m
Command action
   a   toggle a bootable flag
   b   edit bsd disklabel
   c   toggle the DOS compatibility flag
   d   delete a partition
   l   list known partition types
   m   print this menu
   n   add a new partition
   o   create a new empty DOS partition table
   p   print the partition table
   q   quit without saving changes
   s   create a new empty Sun disklabel
   t   change a partition's system id
   u   change display/entry units
   v   verify the partition table
   w   write table to disk and exit
   x   extra functionality (experts only)

Command (m for help):

what the fuck do I have to choose here to make my HD work?

This post has been edited by Ichy: Apr 23 2013, 21:18

Post the output of these:

CODE

lsblk
sudo vgdisplay
sudo pvdisplay

CODE

root@server88-208-193-162:~# lsblk
NAME                           MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                              8:0    0 232.9G  0 disk
  sda1                           8:1    0   243M  0 part /boot
  sda2                           8:2    0   3.8G  0 part [SWAP]
  sda3                           8:3    0     1K  0 part
  sda5                           8:5    0 228.9G  0 part
    VolGroup00-LogVol00 (dm-0) 252:0    0 228.8G  0 lvm  /
sdb                              8:16   0 232.9G  0 disk
  sdb1                           8:17   0 232.9G  0 part /mnt/2ndHDD
  sdb2                           8:18   0  47.1M  0 part
root@server88-208-193-162:~# sudo vgdisplay
  --- Volume group ---
  VG Name               VolGroup00
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               228.83 GiB
  PE Size               4.00 MiB
  Total PE              58580
  Alloc PE / Size       58580 / 228.83 GiB
  Free  PE / Size       0 / 0
  VG UUID               IyhoOj-Hj2a-b4dp-6WC8-VF7j-jIZc-IEfzj1

root@server88-208-193-162:~# sudo pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda5
  VG Name               VolGroup00
  PV Size               228.83 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              58580
  Free PE               0
  Allocated PE          58580
  PV UUID               DJfLmi-3eez-nC25-t3Pc-282u-oheU-CEO1cA

root@server88-208-193-162:~#

This post has been edited by Ichy: Apr 23 2013, 21:18

Extending your logical volume (LogVol00) is easy enough, the problem is doing the same for the filesystem, which needs to be unmounted first. I'm afraid I can't really help on that front.
Alternatively, you can create a new logical volume, format it and then mount it as a separate disk, but I'm guessing H@H wouldn't like that too much (I think? Never used H@H)

Ew, striped LVM. Keep in mind that if you lose one disk with that, you lose everything.

It seems like you did something between the two posts, since it didn't have a sdb2 in your first post, but it's already mounted on /mnt/2ndHDD. You don't really have to do anything else, unless you want it on another mount point.

You don't really have to do anything else, unless you want it on another mount point.

True Tenboro; Ichy, I think you can simply "softlink the new space" into the old H@H cache.

In the directory /h/hl/cache (you are runnign H@H in /h/hl I guess) you should have a bunch of directories numbered from 00 to ff, do du -h on them:

CODE

du -h /h/hl/cache/*

They should have similar sizes, if they don't have similar sizes the following will not work very well.

Now move half of these directories across to the new disk and soft link them back (this command may take some time to complete):

CODE

cd /h/hl/cache
perl -e 'printf "%02x\n", $_ foreach (0..127)' | while read x; do mv $x /mnt/2ndHDD/$x; ln -s /mnt/2ndHDD/$x $x; done

And try booting H@H again. Unless H@H have issues following soft links this shall solve the problem.

EDIT: it's 0..127, not 1..128, to get the first half of directories. Lack of attention will kill me someday.

This post has been edited by blue penguin: Apr 24 2013, 02:20

It seems like you did something between the two posts, since it didn't have a sdb2 in your first post, but it's already mounted on /mnt/2ndHDD. You don't really have to do anything else, unless you want it on another mount point.

Yep I tried some random guide I found but not sure if that worked at all (IMG:[invalid] style_emoticons/default/anime_cry.gif)

I have 3 Clients running on this Server so I think it would be a good idea to just move one of them to the new HD and then give the other 2 more space.
Would this work and how? If now I will try Blue Penguins idea once im back from work.

This post has been edited by Ichy: Apr 24 2013, 04:47