Error Reading Information On Service Mysqld Bad File Descriptor
information on service mysqld: Bad file descriptor Page Title Module Move Remove Collapse X Conversation Detail Module Collapse Posts Latest Activity Search Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new posts macca63 Junior Member Join Date: Oct 2011 Posts: 20 #1 error reading information on service mysqld: Bad file descriptor 11-11-2011, 10:24 AM Hi all 3 days ago I clicked 'upgrade' (rom the web interface) and a whole load of actions started scrolling - an untrained glance looked like all was going OK until it just stopped - but with 'cleanup' being the last line I thought perhaps it had finished but left it alone anyway. Some hours later there was no changed so I powered down (having to hold the power button in to do so) and when I switched back on, the 'active' (HD?) light stays on permanently and I can't access the web interface: "Forbidden You don't have permission to access / on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.2.17 (Fedora) Server at 192.168.0.8 Port 80" And when I try and connect via 'Finder' on my Macbook I get: "There was a problem connecting to the server "Vortexbox" Check the server name or IP address, and then try again" Powering down again and disconnecting the power lead did allow access again for a few minutes - enough to get to the web interface but any actions here give me a pop-up asking if I want to open/save a 'system.php' file (when I open this it's empty). So I'm a bit stuck - especially as I am a new VB owner and have just spent a month ripping around 500 CD's and sorting & importing my iTunes library and had yet to make a backup (I know, I know!) Any advice on how to get things back to pre-upgrade status would be greatly appreciated. I have an SB Touch as my player and I have downloaded 7.6.1 and (I think!) 7.7.0 as it wouldn't let me play anything at all (Spotify, TuneIn, LastFM) without doing so. Here's the log from the upgrade page: Modifying /etc/sudoers to allow user squeezeboxserver to run /usr/local/sbin/spc-wakeup_alt.sh.. Done! Helper scripts installed to /usr/local/sbin and /etc/sudoers has been updated. Updating : tzdata-2011k-0.1.20110921.fc14.noarch 10/54 Updating : php-common-5.3.8-3.fc14.i686 11/54 Updating : rpm-4.8.1-7.fc14.i686 12/54 Updating : rpm-libs-4.8.1-7.fc14.i686 13/54 Updating : php-cli-5.3.8-3.fc14.i686 14/54 Updating : php-5.3.8-3.fc14.i686 15/54 Installing :
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Fedora - Starting snort: [FAILED] boot message - should I be concerned? Want to Advertise Here? Solved Fedora - http://vortexbox.org/forum/vortexbox/help/3007-error-reading-information-on-service-mysqld-bad-file-descriptor Starting snort: [FAILED] boot message - should I be concerned? Posted on 2011-03-26 Linux Linux OS Dev Linux Distributions 1 Verified Solution 10 Comments 744 Views Last Modified: 2012-05-11 Ive no ive what snort is. Thanks, 0 Question by:fcek Facebook Twitter LinkedIn Google LVL 31 Best Solution byfarzanj Become root issue the command ntsysv Find snort. Uncheck (unselect) https://www.experts-exchange.com/questions/26913390/Fedora-Starting-snort-FAILED-boot-message-should-I-be-concerned.html it. Save and exit Go to Solution 10 Comments LVL 31 Overall: Level 31 Linux 22 Linux Distributions 12 Linux OS Dev 10 Message Expert Comment by:farzanj2011-03-26 No. Are you using snort at all? If not, simple issue the command chkconfig snort off And you would not see this message again If you want to see which services start at boot time, issue the following command ntsysv 0 LVL 3 Overall: Level 3 Linux 1 Message Expert Comment by:dileepan_k2011-03-26 You may check this site (http://www.snort.org/) and decide. It is an optional service and need not be worried much 0 LVL 31 Overall: Level 31 Linux 22 Linux Distributions 12 Linux OS Dev 10 Message Expert Comment by:farzanj2011-03-26 Are you doing any packet sniffing? Are you studying any networking packets and looking at network traffic? If not, simply turn the service off. 0 Message Author Comment by:fcek2011-03-29 farzanj: chkconfig snort off error reading info on service snort:: : bad file descriptor? 0 LVL 31 Overall: Level 31 Lin
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://askubuntu.com/questions/815409/error-in-accept-bad-file-descriptor-mysql-error this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask https://forums.amahi.org/viewtopic.php?t=2529 Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can error reading answer The best answers are voted up and rise to the top Error in accept: Bad file descriptor — mysql error up vote 0 down vote favorite After working for years on Ubuntu 14.04 (on OpenVZ) without any problem, I installed a new Ubuntu 16.04.01 LTS running on OpenVZ. I set it up as a LEMP stack. The problem is that after a while (hours), mysqld error reading information starts consuming 100% CPU and the error log is filled with strange 'Error in accept: Bad file descriptor' errors, over and over again, the err file quicly became 4Gb large. MySql needs to be setup for replication. With replication enabled, the bin.err file is written in the same way. I just can't figure out what happens and why. The only thing I did out of the ordinary was to set 'mysqld: ALL' in hosts.deny and 'ALL: LOCAL' and a specific IP in hosts.allow, to allow the replication. Any idea about what's happening? server 16.04 mysql share|improve this question asked Aug 22 at 15:27 Gaspy 11 add a comment| 1 Answer 1 active oldest votes up vote -1 down vote I'm having issues with this, too. It only starts to fill up the log when trying to connect over ssh tunnel to MySQl. I figured out that my /etc/hosts didn't have the proper localhost setup. share|improve this answer edited 2 days ago UTF-8 1,6371924 answered 2 days ago chris mccoy 11 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook
properly work. Fedora 14 Post Reply Print view Search Advanced search 11 posts 1 2 Next sag47 Posts: 43 Joined: Sun Feb 13, 2011 9:27 am [solved] Amahi doesn't properly work. Fedora 14 Quote Postby sag47 » Sun Feb 13, 2011 9:51 am I'm testing Amahi for my home use. When setting up amahi through port 2000 it freezes at 69% Configuring your network (eth0).tail /root/hda-install.log shows.Code: Select allerror reading information on service yum-updatesd: Bad file descriptor
yum-updatesd: unrecognized service
error reading information on service ldap: Bad file descriptor
ldap: unrecognized service
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
Stopping NetworkManager daemon: [FAILED]
Stopping unused services done.
Stopping NetworkManager daemon: [FAILED]I am currently running my Fedora 14 in runlevel 3 without a GUI.Here's the exact method I installed Amahi and Fedora 14.---------------------------------------------------------------------------------------------Boot and install Fedora 14 with default settings configuring server name to amahiserver.Restart the machine and create your user.Disable GUI on start upJust change in /etc/inittab the lineid:5:initdefault:toid:3:initdefault: Here is more information : http://www.fedorafaq.org/basics/#runlevelReboot and do the rest through the terminal runlevel 3.Remove Office/Productivity software...Code: Select allyum groupremove "Office/Productivity"Check for updates.Code: Select allyum check-updateUpdate software.Code: Select allyum updateInstall ssh serverCode: Select allservice sshd status
service sshd startIf there is no sshd status then install openssh server.Code: Select allyum in