Databases, Systems & Networks

Source: Visser Labs Blog

When uploading a set of admittedly large images using NextGEN Gallery to my WordPress site I exceeded my web hosts default memory usage allocation for PHP applications. The error was:

Follow thumbnails could not created. sample.jpg (Error : Exceed Memory limit. Require : 80.65 MByte)

This issue can be resolved by increasing the memory usage allocation at a per-plugin level for PHP applications that require more grunt than others. It’s quick and easy!

1. Open an FTP connection to your root WordPress directory
2. Open /wp-content/plugins/nextgen-gallery/lib/gd.thumbnail.inc.php with your favourite text editor (e.g. UltraEdit, etc.)
3. On line #168 un-comment (remove the //) from before @ini_set('memory_limit', '128M');
4. Save and upload changes
5. Delete image/s that failed to generate a thumbnail and re-upload using NextGEN Gallery’s standard Upload Images feature

If you find 128MB is too ‘conservative’ this can be increased again to any figure of your liking, I find 128MB appropriate for most commercial and personal usage but if you’re a HD photographer then you’re going to hit this limit very quickly… that’s it!

Counterpoint Hackerspace, une bande de geeks localisée à Roswell dans l’état de Georgie aux États unis, a eu l’excellente idée de mettre au point un outil permettant de stocker sur Tor des fichiers, un peu à la manière d’un espace « cloud », mais avec tous les avantages que Tor peut apporter : anonymat, décentralisation et gestion par la communauté. Lire la suite…

The excitement of installing a new version of macOS, especially if it’s a High Sierra 10.13, is only tempered by the possibility of it not working properly or not being compatible with the apps you use most.

Before you begin upgrade to MacOS make a bootable backup

If you haven’t started the process of upgrading yet, check if the Mac is compatible with macOS High Sierra and make a bootable backup. 

Do it now, before you do anything else. If things go disastrously wrong at least you’ll be able to boot from macOS’ Recovery partition and migrate all your data back to your Mac. You can use any backup tool you like – Apple obviously favours Time Machine, but you don’t have to use it. You can use, for example, Get Backup Pro, which comes with your Setapp subscription. Don’t have a Setapp subscription? Click here to sign up.

Common MacOS High Sierra Problems

While most new versions of macOS are relatively problem-free, it’s not unknown for users to have issues – particularly with a beta or .0 release. Thankfully most are easy to resolve. Here’s how to fix the most common High Sierra issues.

High Sierra Installer Won’t Download

If you’re trying to download the macOS High Sierra installer, you’ll need to have signed up to App Store. If you’ve done that, and managed to start the downloading process only for it to fail, force quit the App Store app.

1. Press Cmd-Alt-Esc or go to the Apple menu and choose Force Quit.
2. Select the App Store app and confirm you want to force quit.
3. Re-launch the App Store and try downloading again.

Macos High Sierra Won’t Install

If the download completes successfully but the installation doesn’t finish, force quit the installer using the same procedure as above. 

1. Restart your Mac
2. Launch the App Store app and go to the Purchases tab. 
3. Find macOS High Sierra and click Install. 

If that doesn’t work, try deleting the downloaded installer (it’s in your Applications folder) using CleanMyMac and download it again.

If you have a copy of macOS Server in your applications folder, that may be the root of the problem. Delete it and try again.

Lire la suite…

Mon NAS Synology vient de mettre à jour son firmware DSM et je constate en lançant ma sauvegarde rsync que la connexion rsync vers le NAS ne se fait plus : après saisie du mot de passe, on obtient une erreur “permission denied”.

Voici comment remédier à ce petit désagrément en deux minutes montre en main.

Problème : connexion SSH refusée

Lors de la connexion initiale, démarrée par :

rsync --ignore-existing --progress -vr --rsh='ssh -p22222' /home/backup/* root@example.com:/volume1/video

on obtient le message d’erreur suivant, après saisie du mot de passe:

Permission denied, please try again.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]

Après vérification que les identifiants (user/password) sont bien corrects, il s’avère que la solution réside dans l’utilisation de l’argument --rsync-path afin d’expliciter le chemin de l’exécutable rsync présent sur le NAS.

Lire la suite…