Re: [gentoo-user] [slightly O/T] mysql problems
On Wednesday, October 15, 2014 09:40:56 PM Mick wrote: On Wednesday 15 Oct 2014 13:41:03 Kerin Millar wrote: Database changed mysql DROP TABLE `website1@002dnew`.`actions`; Is this a table for which it is also complaining that a corresponding tablespace doesn't exist in database `website1@@002dnew`? Your original post mentioned only a table named `webform_validation_rule_components`. Yes, there are loads of tables that it is complaining about. However, the name of the database mentioned in the logs is not that of the local machine, but of the remote. Whichever table(s) it is complaining about, if you happen to find a corresponding .idb file in a different database (sub-directory), you might be able to satisfy MySQL by copying it to where it is expecting to find it. If that works, you should then be able to drop it. I lost you here. We have the local database, website_test. In it I can see a number of tables. I also have other databases for different websites. Where am I supposed to look for corresponding .idb files? Sometimes, directly copying an InnoDB tablespace into place requires a more elaborate procedure but I won't muddy the waters by describing said procedure just yet. ERROR 1051 (42S02): Unknown table 'actions' mysql DISCARD TABLESPACE `website1@002dnew`.`actions`; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DISCARD TABLESPACE `website1@002dnew`.`actions`' at line 1 = I think in mysql-5.5 I should be using DROP TABLESPACE instead? My mistake. The correct syntax for discarding the tablespace would be: ALTER TABLE table DISCARD TABLESPACE; I'm stating the obvious here, but be sure not to DROP or DISCARD TABLESPACE on a table whose tablespace does exist and for which you do not have a backup. Both commands are destructive. Well, I still have the backup from the live website, I can restore from it if I have to. However, what I find confusing is that the errors mention the live website's database name, not the local database. Shouldn't the import function import the tables into the local database? When you do it as you said: mysql -u webadmin -h localhost -p website_test website1_20141014.sql then that is the expected result (that it uses tables in the local database.) Can you do a search in the SQL-file for references to the remote database and post some of those lines? (Preferably only a subset referencing a single table) -- Joost
Re: [gentoo-user] [OT] Six non-Gentoo installs
On Tue, Oct 14, 2014 at 6:36 PM, Grant Edwards grant.b.edwa...@gmail.com wrote: CentOS 7.0, however, was a mess. It took three attempts and almost an entire day of work. My first attempt was to use the minimal ISO image so that I would have the option of burning a CD if needed (I can't burn DVDs at the moment). That was a mistake. It was too minimal, and I couldn't get the network working to the point where I could configure repositories and install other stuff. Since the CentOS 7 ISO images all boot from USB flash drive anyway, staying under the 700MB CD size limit was moot anyway. Next I tried the net install ISO. I'm guessing I could have burned the DVD image to USB drive, but all I want is a minimal desktop system, so I figured why wait for a download of 3.5GB of stuff I don't care about. It still didn't recognize the NVidia Ethernet controller on my 5-year-old motherboard. After some cable swapping and futzing around, I got the netinstall going using the Realtek NIC. Maybe I just got unlucky and picked a slow mirror site, but once I got the install going, it ran for over 3 hours when installing a vanilla Gnome desktop system. Compare that with a 15 minute download time for a 700MB Xubuntu CD and then a 15 minute install. AFAIK, the netinstall isn't really meant to be used over the net but with a local mirror. CentOS 7 refused to install the bootloader in a partition: your only choices are MBR or nothing. When I manually installed grub legacy it failed because I had stupidly allowed CentOS to use ext4, and the build of Grub I had laying around didn't grok ext4. So I re-do the whole net install again using ext3 instead. Now, after manually installing Grub legacy in the CentOS 7 partition, it boots up. The Anaconda developers have the same design philosophy as the Gnome developers: fewer options, fewer options, fewer options, fewer options, ... In this particular case, they're just following the grub developers' dislike of block lists; and the ext4 maintainer's described them as emotionally insecure because of that. CentOS still doesn't recognize the NVidia motherboard Ethernet controller. After Google finds me a pages full of links to other people complaining about the exact same thing, I find out RedHat decided that the NVidia forcedeth driver wasn't widely used enough to deserve inclusion on an ISO image that was already 360+ MB. Thanks for that, RedHat. So it takes another 45 minutes of faffing around finding a third party src.rpm file for the forcedeth module and installing it. [It was either that or build a kernel and initrd.] For future reference, elrepo.org is the best repo for RHEL issues like this one. For RH, dropping forcedeth means cutting its support costs.
[gentoo-user] dev-python/setuptools sandboxviolation
Hi,
I'm having problems (re)installing dev-python/setuptools-2.2 on my hardened
gentoo. For python3.3 everything works. But with python2.7 I always get a
SandboxViolation.
emerge output:
Best match: PasteDeploy 1.5.2
Downloading
https://pypi.python.org/packages/source/P/PasteDeploy/PasteDeploy-1.5.2.tar.gz#md5=352b7205c78c8de4987578d19431af3b
Installing easy_install script to
/var/tmp/portage/dev-python/setuptools-2.2/image//_python3.3/usr/lib/python-exec/python3.3
Processing PasteDeploy-1.5.2.tar.gz
Writing
/var/tmp/portage/dev-python/setuptools-2.2/temp/python2.7/easy_install-yPW_DV/PasteDeploy-1.5.2/setup.cfg
Running PasteDeploy-1.5.2/setup.py -q bdist_egg --dist-dir
/var/tmp/portage/dev-python/setuptools-2.2/temp/python2.7/easy_install-yPW_DV/PasteDeploy-1.5.2/egg-dist-tmp-vav2_N
error: Setup script exited with error: SandboxViolation:
mkdir('/var/tmp/portage/dev-python/setuptools-2.2/work/setuptools-2.2-python2_7/build/PasteDeploy.egg-info',
511) {}
I also tried disabling sandoxing in FEATURES, but the error still occurs:
FEATURES=parallel-fetch parallel-install -userpriv -usersandbox -sandbox
-strict
I tried other versions but the behaivour was the same.
Any ideas?
--
regards
alex
Re: [gentoo-user] has anyone tried KDE5?
On 10/14/2014 01:16 PM, Alan McKinnon wrote: Not really strange - I got something similar with dolphin too. I use NFS mounts in dolphin a lot (not using the built-in nfs kpart, it's a traditional mount). Double clicking through on folder names would often select everything from where the cursor landed to the top of what is shown in the dolphin window. F5 refresh, or Alt-left and Alt-right wouldn't change anything (I assume some caching is involved). But, clicking away from the current pane to some other folder outside the nfs mount, then re-navigating back to it would make the issue go away. This is exactly the issue I have but it isn't with an NFS mount, it's with a mount to my raid device (actual full 3ware RAID card, not a fakeraid.) I keep this ~amd64 system quite current (update twice weekly or so) and haven't run into this again for about 6 weeks now. Looks like someone fixed something, in whole or in part. I don't update that often, generally once a month I update. Maybe sooner than that, but not once a week. I usually exclude mythtv until I have enough time to upgrade the backend and all frontends at the same time, but I am going to have to do a full update including mythtv really soon as Tribune (and as such, schedulesdirect) do not offer the old XML TV listings as of November 1. Sigh... That aside, when I do this major update on all of my PCs maybe the issue will finally go away. Dan
[gentoo-user] Re: [systemd] Is this a NetworkManager bug?
On 10/15/2014 08:23 PM, Tom H wrote: On Mon, Oct 13, 2014 at 7:39 PM, walt w41...@gmail.com wrote: I just switched my home LAN from wired to all wifi and I'm having trouble with NetworkManager at boot time. I have systemd start NetworkManager at boot because I need the internet for ntpdate and to start the nfs server for the LAN. Before I switched to all-wireless this method worked perfectly, but no longer. After bootup I see that NetworkManager started wpa_supplicant in the background, but apparently does *not* run dhcpcd. (The wlan0 is up but it has no IP address and the routing table is empty.) As an alternative to NetworkManager I can have systemd start dhcpcd at boot, which almost (but not quite) works well enough. This causes a race condition because wlan0 takes several seconds to come up properly and by then both ntpdate and nfs-server have already run and failed. So, I asked myself, why not have systemd start dhcpcd at boot in addition to NetworkManager? The reason that fails is that they both start wpa_supplicant in the background and the two instances interfere with each other. Anyone see a way around this catch22? Do you have All users may connect unticked in the NM applet or permissions=user:walt:; in the NM connection's config? After studying the logs I'm beginning to think that NM is actually trying to start wlan0 at boot time but failing with this message: 'no secrets', which I assume means no password, maybe? Yes, I do have the all-users box ticked. Question: I've set up the wlan0 connection (as root) several times using nmtui, including the SSID password, yet each time I start nmtui the password field is blank again. Is this normal behavior? How can I tell if the password is actually being stored somewhere? Thanks.
[gentoo-user] Re: New wireless adapter breaks nfs exports
On 10/15/2014 12:57 PM, Tom H wrote: On Tue, Oct 7, 2014 at 7:39 PM, walt w41...@gmail.com wrote: On 10/05/2014 08:31 PM, Tom H wrote: On Sat, Oct 4, 2014 at 2:52 PM, walt w41...@gmail.com wrote: This machine (my nfsv3 file server) just got a new wireless adapter, which works fine for everything except serving files :( mount.nfs: requested NFS version or transport protocol is not supported google shows me lots about slow nfs connections over wireless but nothing about non-support. I'm using only nfs3 ATM because I've had so many problems with nfs4 in the past. I thought I'd ask here if nfs4 might fix the problem before changing everything. NFS works over wifi. Have you tried mounting with -v and/or -o nfsvers=3? Yes, about 30 seconds ago :) #mount -v -t nfs -o nfsvers=3 a6://usr/portage /mnt mount.nfs: timeout set for Tue Oct 7 16:35:39 2014 mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.75' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying 192.168.1.75 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 192.168.1.75 prog 15 vers 3 prot UDP port 36168 mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported I have nfsv4 working correctly so the urgency is gone but I'm still curious if nfsv3 really should work over wifi as well as nfsv4. Both nfsv3 and nfsv4 work over wifi. Do both the client's and the server's kernels have nfsv3 enabled? From the output above I'd check the client's kernel config. The problem turned out to be incorrect nfs useflags, not kernel config, and nfsv3 is working now, thanks much.
Re: [gentoo-user] Re: [systemd] Is this a NetworkManager bug?
On Thu, Oct 16, 2014 at 3:53 PM, walt w41...@gmail.com wrote:
On 10/15/2014 08:23 PM, Tom H wrote:
On Mon, Oct 13, 2014 at 7:39 PM, walt w41...@gmail.com wrote:
I just switched my home LAN from wired to all wifi and I'm having trouble
with NetworkManager at boot time.
I have systemd start NetworkManager at boot because I need the internet
for ntpdate and to start the nfs server for the LAN. Before I switched
to all-wireless this method worked perfectly, but no longer.
After bootup I see that NetworkManager started wpa_supplicant in the
background, but apparently does *not* run dhcpcd. (The wlan0 is up
but it has no IP address and the routing table is empty.)
As an alternative to NetworkManager I can have systemd start dhcpcd
at boot, which almost (but not quite) works well enough. This
causes a race condition because wlan0 takes several seconds to come
up properly and by then both ntpdate and nfs-server have already
run and failed.
So, I asked myself, why not have systemd start dhcpcd at boot in
addition to NetworkManager?
The reason that fails is that they both start wpa_supplicant in
the background and the two instances interfere with each other.
Anyone see a way around this catch22?
Do you have All users may connect unticked in the NM applet or
permissions=user:walt:; in the NM connection's config?
After studying the logs I'm beginning to think that NM is actually
trying to start wlan0 at boot time but failing with this message:
'no secrets', which I assume means no password, maybe?
Yes, I do have the all-users box ticked. Question: I've set up the
wlan0 connection (as root) several times using nmtui, including the
SSID password, yet each time I start nmtui the password field is blank
again. Is this normal behavior? How can I tell if the password is
actually being stored somewhere?
As I said some messages ago, check:
/etc/NetworkManager/system-connections
In that directory should be all the system-wide network
configurations. Also, check
/etc/NetworkManager/NetworkManager.conf
and make sure you have plugins=keyfile in the [main] section. At
some point NM had integration with the OpenRC network configuration,
and (AFAIR) sometimes it made a mess inside /etc/conf.d. I don't know
if such integration exists anymore; nowadays I don't even have
/etc/{conf,init}.d, and everything works so much better.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [systemd] Is this a NetworkManager bug?
On Thu, Oct 16, 2014 at 4:53 PM, walt w41...@gmail.com wrote: On 10/15/2014 08:23 PM, Tom H wrote: On Mon, Oct 13, 2014 at 7:39 PM, walt w41...@gmail.com wrote: I just switched my home LAN from wired to all wifi and I'm having trouble with NetworkManager at boot time. I have systemd start NetworkManager at boot because I need the internet for ntpdate and to start the nfs server for the LAN. Before I switched to all-wireless this method worked perfectly, but no longer. After bootup I see that NetworkManager started wpa_supplicant in the background, but apparently does *not* run dhcpcd. (The wlan0 is up but it has no IP address and the routing table is empty.) As an alternative to NetworkManager I can have systemd start dhcpcd at boot, which almost (but not quite) works well enough. This causes a race condition because wlan0 takes several seconds to come up properly and by then both ntpdate and nfs-server have already run and failed. So, I asked myself, why not have systemd start dhcpcd at boot in addition to NetworkManager? The reason that fails is that they both start wpa_supplicant in the background and the two instances interfere with each other. Anyone see a way around this catch22? Do you have All users may connect unticked in the NM applet or permissions=user:walt:; in the NM connection's config? After studying the logs I'm beginning to think that NM is actually trying to start wlan0 at boot time but failing with this message: 'no secrets', which I assume means no password, maybe? Yes, I do have the all-users box ticked. Question: I've set up the wlan0 connection (as root) several times using nmtui, including the SSID password, yet each time I start nmtui the password field is blank again. Is this normal behavior? How can I tell if the password is actually being stored somewhere? I've never used nmtui (I didn't even know about it). This the config that I use when i visit my parents (I use a static address at home so this corresponds to your use-case). It has to be in 0600 mode for NM to use it. # cat /etc/NetworkManager/system-connections/mumdad [connection] id=mumdad uuid=da59ada3-1349-49fe-b63b-bc68f67b6f89 type=802-11-wireless [802-11-wireless] ssid=number96 mode=infrastructure security=802-11-wireless-security [802-11-wireless-security] key-mgmt=wpa-psk psk=x [ipv4] method=auto dns=8.8.8.8;8.8.4.4; [ipv6] method=link-local You have to have plugins=keyfile in the [main] section of /etc/NetworkManager/NetworkManager.conf for the above to work.
