SliTaz Forum
You are not logged in.
Pages: 1
Please, announcing what comes with the site?
The last two days it worked very slowly.
Now it is unavailable.
It seems that the other sites in the SliTaz network working properly.
Offline
I had to switch to another default from mirror.slitaz.org yesterday because tazpkg wouldn't recharge.
Mirror.slitaz.org appears to be back up to speed since pkgs.slitaz.org was taken off line.
Offline
Requests flood saturday near 3am and friday near 0am: http://mirror.slitaz.org/info/graphs.php?stats=net#net
Added robots.txt, tried lighttpd config parameters
server.kbytes-per-second = 128
server.max-worker = 3
without success.
Any idea ?
Offline
No, any good idea, Pascal. I see growed number of connections, possibly attack? Ok, let it be in offline some time.
But I need search possibilities of pkgs.slitaz.org while I working under receipt creation and debugging. Can anyone tell me, what files I actually need to set up my local pkgs server? (I can successfully run http://localhost/pkgs/search.sh, and I prepared /home/slitaz/... folders, and filled them with files (/home/slitaz/stable/packages/[files.list.lzma, packages.desc, packages.equiv, packages.list, packages.md5, packages.txt] and so on). No, I can read at bottom '0 packages and 426822 files in stable database". Why 0?
Offline
Check your $WOK variable and/or clone hg in /home/slitaz/stable/wok, or create symlink.
http://hg.slitaz.org/slitaz-forge/file/17fc1a40d7da/pkgs/mirror-search.sh#l250
http://hg.slitaz.org/slitaz-forge/file/17fc1a40d7da/pkgs/mirror-search.sh#l179
Offline
Bellard: Check the server for accounts, scripts and processes you didn't create.
Something similar happened to my server 3 weeks ago that forced me to restart the server box manually so I could log in. When I logged in I found several accounts with root access, a handful of DDoS scripts written in Bash and the log told me that I was getting hit by about 8Mbits/s. I figured this is what happened: The root account got hacked, these scripts installed to DDoS another server and the server DDoS with a low-level attack to hide the fact, not trigger the host's automated defences and make it hard to login via ssh impossible.
Offline
Well ... like you know i'm a newbie on linux & i dont have knowlegde to do that, but is not possible to do a "Flooding Defense" ?
My idea is that a DDOS atack, is too many ping requests, so, if we can make a script that only autorize ping requests with for example 10 seconds delay, the DDOS atack cant be done with success.
I know that my idea its not a " Profissional " idea, but mean whyle i thing that is a good idea.
Offline
Thank you, Pascal! I already set links to my local wok clone. No result.
It's something related to read permissions of server.
If I run in terminal [c]/var/www/pkgs/search.sh[/c] then I can see html source with a lot of packages (run both as root and tux), but see 0 in page.
I saw in debug mode that $WOK sets correct. I added to page footer next code:
echo $WOK
cd $WOK
ls
and I see correct $WOK but content of my /var/www/pkgs folder.
By the way, my local clone of wok is in separate partition (have small HDD full of stuff).
___
P.S.
It seems like my busybox's httpd server is "chrooted" in the /var/www folder. I use same httpd that served tazpanel, but seems I need to set up separate server...
____
P.P.S.
Not, really not "chrooted". And it works if I copied wok instead of making symlink. This situation forced me to writing my own tool suitable to my only needs 
Offline
The host has the (annoying) habit of nulling an IP if it gets attacked by a large enough DDoS. It works pretty well, but in this case it didn't activate. Hopefully the same thing is not happening to Bellard's server.
Offline
Another VM was eating most CPU time.
The story : an external mirror start rsyncing, mirror VM cpu goes 100%, http requests are delayed, requests backlog grows up...
http://pkgs.slitaz.org/ is back. User authorized_keys files are restored.
Offline
and also tank is down I dont know, if it has any connection
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]