Mount Drobo 5n from Ubuntu 14

Had to do some searching to figure this out, so I’m noting it here for future reference. Even though smbclient -L works just fine, mounting with smbmount or mount -t was just not working.

apt-get install cifs-utils
mount.cifs -vv //192.168.0.3/backup /mnt/drobo/ -o user=Admin

it prompts for Admin’s password, then voila.

Posted in Uncategorized | Leave a comment

WordPress permalinks in nginx subfolder

Was having some trouble hosting a wordpress site from a subfolder of the domain, ‘/blog’. The permalinks just would not work until I found this solution:

I only had to adapt it slightly for my situation:

location /blog/ {
try_files $uri $uri/ /blog/index.php?$args;
}

I had tried several other solutions but they had results such as losing the css. This worked for me!

Posted in Uncategorized | Leave a comment

Just another wordpress child theme instruction / white page of death cure

Carelessly following these instructions, I got a WPOD.
Turns out the reason was I was copying two sections where I really only needed the second.
For the not-so-faint-of-heart;
make your child folder, such as ‘twentyten-child’ (2010, old-school, I know!)
Then you need two files to get started; style.css and functions.php as follows:

style.css
/*
Theme Name: TwentyTen Child
Theme URI: http://example.com/twenty-ten-child/
Description: TwentyTen Child Theme
Author: Joe T
Author URI: http://www.omniweb.com/wordpress
Template: twentyten
Version: 1.0.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Tags: Blargh, light, dark, two-columns, right-sidebar, responsive-layout, accessibility-ready
Text Domain: twenty-ten-child
*/

and functions.php

function theme_enqueue_styles() {

$parent_style = 'parent-style';

wp_enqueue_style( $parent_style, get_template_directory_uri() . '/style.css' );
wp_enqueue_style( 'child-style',
get_stylesheet_directory_uri() . '/style.css',
array( $parent_style )
);
}
add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' );

?>

Then add any other files you need to customize and you’re safe from the upgrade destruction monster. Just good idea to keep an eye on when the parent theme is updated, what files are updated and make concurrent changes in any customized files (scary! but do it anyway you lazy lug [to myself]) -bye

Posted in Uncategorized | Leave a comment

Can’t upload as different user with VSFTP

Running vsftpd on CentOS, a user was unable to upload a file to a folder for which the user had group permissions.

Thanks to this post here, I was able to figure it out.

Needed to edit vsftpd.conf and update to include the following lines:

local_umask=002
file_open_mode=0777
anon_upload_enable=YES
anon_mkdir_write_enable=YES

After restarting vsftpd and making sure the relevant folders are group-writable, it works!

Posted in Uncategorized | Leave a comment

perl’s File::PID trickiness

I have a program that uses perl’s File::PID but I was having some issue where the program would occasionally start multiple times.

Finally today I spent some time to figure out what’s going on. It seems that if you use the '$pidfile->write' function after checking whether it’s running already with '$pidfile->running()' then it puts back NOT the PID of the currently running process, but the PID that was there before!

Unless I’m misunderstanding my test result, you (I) need to do this to get the new PID into the old pidfile:


use File::Pid;
my $pidfile = File::Pid->new({
file => '/var/run/upload_cdn.pid',
});

my $num = $pidfile->running();

if ( $num ){

die "already running: $num\n\n";

} else {

$pidfile->remove;

my $pidfile2 = File::Pid->new({
file => '/var/run/upload_cdn.pid',
});

my $pid = $pidfile2->write;

if( $pid ){
&_log("Now running with PID $pid\n");
}

}

#$pidfile->write; ## This was putting the original non-running PID back into the file

Maybe I was doing something wrong or maybe there’s a better way to handle this? Hopefully my program won’t start running multiple times any more!

Posted in Uncategorized | Leave a comment

Failed to prepare The drive Y:\ does not exist!

While trying to run automated backups with syncbackfree some systems were having the subject error.

According to this forum the problem is with trying to use a mapped drive. I changed it to the LAN ip address
\\192.168.0.100\

and we’ll see if that doesn’t resolve it.

Posted in Uncategorized | Leave a comment

Trouble Installing XML::Parser on CentOS

While trying to install XML::RSS from CPAN on a CentOS installation with Perl 5.10, it kept failing on the pre-requisite XML::Parser

For example, one of the failures showed:

t/astress.t ……….. Failed 15/27 subtests

and concluded with

Test Summary Report
——————-
t/astress.t (Wstat: 0 Tests: 27 Failed: 15)
Failed tests: 5-11, 14, 18-24
Files=15, Tests=141, 1 wallclock secs ( 0.07 usr 0.03 sys + 0.88 cusr 0.14 csys = 1.12 CPU)
Result: FAIL
Failed 1/15 test programs. 15/141 subtests failed.
make: *** [test_dynamic] Error 255
TODDR/XML-Parser-2.43.tar.gz
/usr/bin/make test — NOT OK
//hint// to see the cpan-testers results for installing this module, try:
reports TODDR/XML-Parser-2.43.tar.gz
Running make install
make test had returned bad status, won’t install without force

To resolve this, I found the doc said

“You can install this module from OS package too, but CPAN has most fresh version.
CentOS/RHEL/Fedora: perl-XML-Parser

so based on this I used
yum install perl-XML-Parser
to install the Perl XML Parser, and that then allowed
cpan XML::RSS
to finally complete the install correctly.

Posted in Uncategorized | Leave a comment

asn1 encoding routines:ASN1_item_verify:unknown message digest algorithm

A process using curl (rtorrent) was giving the subject error after the remote system updated their secure cert from SHA1 to SHA256.

this page provides an answer; openssl needs to be updated: “It requires at least OpenSSL 0.9.8o for a total management of SHA256″

On top of that, (on Ubuntu jaunty) curl needed to be installed from source and the libcurl libraries were updated to get this working again.

Posted in Uncategorized | Leave a comment

Windows 7 PC can’t access Samba Share

In the local network, we have a samba share that doesn’t require a password. Most computers can access this share without any trouble. For some reason a new machine running Windows 7 Professional can’t access it without seeing a login box. Seems there are a lot of people who’ve had this or similar issues, and a lot of potential solutions.

Change made based on this page: In the Local Security Policy, Security Options, change “Network security: LAN Manager authentication level” (new setting: Send LM & NTLM – use NTLMv2 session security if negotiated)

Change made based on this page: In the Local Security Policy, Security Options, change “Microsoft network client: Digitally sign communications (always)” (new setting: Disabled)

Change made based on this page: In the Local Security Policy, Security Options, change “Network security: Minimum session security for NTLM SSP based (including secure RPC) clients” to “No minimum”

I tried a bunch of things including these above – one of them must’ve fixed it but the password box was still popping up; finally i entered ‘x’ as the username and ‘x’ as the password, miraculously it decided to let me in, whereas if I tried leaving it blank, it wouldn’t let me in. Possibly rebooting might have avoided that trouble? What a pain! But now I’m in, ahhhh.

Posted in Uncategorized | Leave a comment

Fix MySQL Replication: Could not parse relay log event entry. The possible reasons are:

After power failures, our MySQL slaves sometimes stop replicating. The error is:

Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.

In the past, I would restore replication from another slave, but this method seems much better in that it’s faster and easier.

Get the Relay_Master_Log_File and Exec_Master_Log_Pos from “show slave status\G”;

reset slave to that point, and let it recover by itself as follows:
Be careful, using Relay_Master_Log_File value from “show slave status\G” for master_log_file, not Master_Log_File value. They’re the same in this case.

mysql> slave stop;
Query OK, 0 rows affected (0.00 sec)

mysql> change master to master_log_file=’LBMS-bin.000012′,master_log_pos=221245113;
Query OK, 0 rows affected (0.04 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

Posted in Uncategorized | Leave a comment