Archives

All posts for the month January, 2014

Another fun filled day with mysql..fuck me.   Anyhow my datadir was filling up and attempted to move datadir to another partition with more space…normally a 2 minute deal.  Update in /etc/my.cnf and restart mysql… negative Houston, we have a problem…Checked all the normal crap with selinux, proper perms on new datadir, owned by mysql.mysql etc…etc.

If you leave the default location /var/lib/myql it will start all damn day and no issues.

Looks like perhaps the Fedora 19 Updates repo has the funky RPMS.  I uninstalled completely and re-installed with yum install mysql mysql-server (which installs the mariadb mariadb-server) numberous times and everytime issues after I moved the datadir.

Here’s the fix..

Used Fedora 20 repo located here.   This did the trick..had one more issue with mysql client it was complaining about not being able to find mysql.sock.  However it did work if I did mysql -u root -p -h 127.0.0.1 but gave error without the -h host portion.   Simple fix.. add this to /etc/my.cnf

[client]

socket=/path/to/mysql.sock

I was literally pulling my hair out , and must have re-installed apache and phpMyAdmin multiple times and tried multiple hosts..    The fucking wiki docs for phpMyAdmin say the configuration file config.inc.php should be in the same directory that index.php is in.  Actually according to those fucking docs theres multiple locations inside that tree  /, ../library, and you can create a directory called config and put the file there.   They say just copy the config.sample.inc.php to config.inc.php and edit that file with your mysql settings..blah blah blah..  Sadly, all the forums and suggestions from those forums..all had you updating those files somewhere in /usr/share/phpMyAdmin tree as well.  WTF.  I’m sure each Linux distro might be a little different, but using Fedora 19.

Yeah none of that shit works at all..fucking wasted half my day on this crap..

The configuration file is in /etc/phpMyAdmin/config.inc.php, updated that ..and tried it and bingo.

I tried about 10 different methods from peoples suggestions on getting my Xbox One to get the network to be an Open Nat, instead of the damn strict NAT and I had a hell of a time getting this to work…finally found this thread on dslresports.com and it worked like a charm.

i have to thank pfsense forum user (and dslr forum user) AhnHEL (he actually found my original post, here, on dslr), he sent me a PM and gave me step by step directions and everything worked, NAT is now reporting as open for the xbone.

just as his directions stated, i recommend putting any settings back to how they were, assuming you followed others threads/directions with no luck. i changed all my settings back to what they were prior to making this thread and followed his directions. the only thing i had to do was pull the power plug from my xbone. after following the steps, the nat went from strict to moderate, but i ran the rest after power cycling the xbone and nat switched to open.

dhcp mapping will work, but i statically set my xbone to an ip outside of the DHCP scope instead.

quote:


Ok, I dont know what you still have setup while you were trying to get this to work but remove any port forwards or rules that you created previously. We’re going to try the UPnP method because its the easiest method to configure. Keep your XBone off while setting this up.

1. I’m sure you have done this, but setup a static DHCP mapping for your XBox One. In my settings below this is 192.168.39.17

2. Now go to Firewall: NAT: Outbound and select Manual Outbound NAT and hit save. This should at default create two entries a LAN mapping and a Localhost mapping.

3. Now add a mapping for your XBox One’s static DHCP IP address on your LAN interface with a /32 as a mask bit in the Source section. In the Translation section of this mapping, select the “Static Port” checkbox. Give the mapping a name like XBone AON and save.

4. Now take this XBone AON mapping rule and move it ABOVE your Default LAN mapping and hit Save.

5. Go to Services: UPnP & NAT-PMP and setup as follows: check enable upnp and nat-pmp, check allow upnp port mapping, external interface, WAN, interaces, LAN, user specified permissions 1, allow 88-65535 192.168.39.17/32 88-65535 Then hit Change.

6. Now to be sure no states to the XBox are lingering from a previous connection, go to Diagnostics: Reset state and Reset.

7. Now fire up your XBox and you should be at NAT Open. If not, double check your settings and if you have a managed switch on your network, disable Multicast filtering on the switch.


regarding number 6, as stated i power cycled off my xbone, clearing the states was not enough.

regarding number 7, the xbone is connected to a managed switch, but i did not need to change any settings on the switch.

thanks again, AhnHEL.

 

Here’s the entire thread.

The only issue I had was turning off the verify certificate and setting that to no.

$ lftp -p 990 bigbeav@ftps.servnername.com
Password:
lftp bigbeav@ftps.servername.com:~> ls
ls: Fatal error: Certificate verification: Not trusted
lftp bigbeav@ftps.servername.com:~> set ssl:verify-certificate no
lftp bigbeav@ftps.servname.com:~> ls
drwxr-xr-x 2 ftp ftp 48 Jan 21 21:24 bin
lftp bigbeav@ftps.servername.com:/>