I have installed transmission on a headless server. I am using transmission-daemon and connects to the webclient on the LAN. However from WAN I can't connect. I have forwarded port 9091 in my router and it connects with the server, but I get 403: Forbidden.
i installed transmission on my fedora14 VPS for headless usage by "yum install transmission transmission-daemon", problem comes when i try to configure the init.d Scrip for transmission-daemon to run as a different user instead of the pre-specified user �transmission�,how should i modify the default transmission-daemon file bellow?
I've installed transmission-daemon on my headless Ubuntu 11.04 server and use the web interface to manage it. This is all working fine. However, after a reboot it seems that transmission daemon starts but the webinterface is unavailable. I get this in the syslog after a reboot:
Code: Jun 22 10:54:27 localhost transmission-daemon[703]: Transmission 2.31 (12441) started (session.c:706) Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:805) Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:982) Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Whitelist enabled (rpc-server.c:986) Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Password required (rpc-server.c:989) Jun 22 10:54:27 localhost transmission-daemon[703]: Port Forwarding Stopped (port-forwarding.c:181) Jun 22 10:54:27 localhost transmission-daemon[703]: UDP Failed to set receive buffer: requested 4194304, got 262142 (tr-udp.c:75) .....
I would like to be able to simply run a shortcut file or batch file in a windows os to start or stop my transmission-daemon.I was thinking about using putty to auto login and execute a file using the -m switch. A problem I am running into is that /etc/init.d/transmission-daemon stoprequires the use of sudo.That would require entering a password which would be automated and insecure or would require manually typing int he password.
I have the Shorewall firewall running on Ubuntu 10.10 server and the issue I am having is the firewall is blocking traffic from my transmission-daemon even though I have allowed it in the /etc/shorewall/rules.
as you can see, Shorewall is rejecting packets with source and destination port 51413 on incoming net2fw and outgoing fw2net even though the rules are set to accept.
I installed ActiveMQ, set up an init.d script and was able to start | stop | restart ActiveMQ from the init.d script. However, when I tried to use:
>sudo chkconfig --add activemq
upstart seemed not to like it. Having NO documentation on how to create a daemon that works with Upstart on the Ubuntu forums, I'm wondering if anyone has any idea why my init.d script doesn't convert.I'm using Ubuntu 10.x.x but this happens on 9.x.x also.
Here is my script..
Code:
#!/bin/bash # ### BEGIN INIT INFO # Provides: activemq
i am succesfully installed TeamSpeak 3 server and now i want to startup it automatically without screen daemon and on every startup on linux ubuntu 9.10 i am using this command for start the TS3 server:./ts3server_linux_amd64 dbplugin=ts3db_mysqlin home/user/Desktop/ts3server_linux_amd64
I'm having some problems getting my screensaver to work automatically.If I start the screensaver config program then it gives me this message: "The XScreenSaver daemon doesn't seem to be running on display ":0.0". Launch it now?" If I click yes then my screensaver works exactly as expected.How can I get the XScreenSaver daemon to start automatically?
I used my boot disk in rescue mode to solve this, but I would really like to know how to do this the easy way.
Question: when I am booting up and getting all those "OK" green remarks, how do I cancel a daemon that freezes instead of giving me an ok or failed? I have tried <Ctrl><C> with no joy. I have tried dropping to interactive mode ("I") and bypassing the bad daemon, but interactive mode freezes when I go to start GDM, so no joy there either.
I've added httpd to runlevels 2-5 using chkconfig, and also double checked it using ntsysv, but it still won't run on startup, even though it works just fine when started manually (using "sudo service httpd start").The results of "chkconfig --list httpd" show it is on for levels 2-5, and I've confirmed the current runlevel to be 3. I've found no errors in the logs (neither Apache's nor the system's), but maybe I'm looking at them wrong...My machine is a VPS (on VMWare) running CentOS 5.5 32bit. For additional information, see the output of getinfo.sh: http://pastebin.centos.org/35570I would greatly appreciate help on this, as it is delaying our NGO from moving servers.
I can only access the Transmission web interface while the Transmission-gtk client is running. When I close it, the web interface is no longer available. I try to manually start the transmission-daemon, but the process never shows up as running.
Originally Posted by uselpa Why do you absolutely want to remove it? There is no good reason for Avahi-daemon to be automatically installed on a server that is setup up with a static ip address. Also, I would like to someone to explain the loqic in having such a service on a server running an Oracle Database.
All of the servers I manage run a bare minimum footprint. Unnecessary services waste server resources and they are potential security risks if not updated.This is why I want to "absolutely" remove the Avahi-daemon.
Dave Walden Linux Systems Administrator CARFAX, INC.
Karmic - When I start up and log in, a window for KDE Desktop Sharing Invitation automatically pops up.
Closing it doesn't prevent it from popping up on next startup.
There doesn't appear to be any option to "Don't show on startup."
When I go to System -> System Settings -> Advanced -> Autostart, it does not appear under Desktop File. The only thing that appears under "Script File" is gtk-2-engines-qtcurve.rc.sh gtk2engines... which does not appear to be the issue.
I'm guessing there's a shell command that will give me a more in-depth look at what should and should not run upon startup? Would really like to startup with a clean screen!
I have installed mysql server on my Ubuntu Lucid AMD64 desktop. I need to run this service only on need. So I prefer not to have this in startup. So I did the following -
1. Deactivated the row entry by name "mysql" from application BootUp-Manager.
2. Run the application sysv-rc-conf and unchecked the checkboxes for all run levels.
3. Run the command "sudo update-rc.d -f mysql remove". Execution completed successfully.
4. Run the command - "sudo service mysql stop". In return I got a message "mysql stop/waiting".
5. Restarted the desktop.
Now when I read through the task manager, I still see a process by name "mysqld" running. I ran the command as mentioned in # 4 above and got the same response. I wanted to know how do I turn off mysql service running from startup permanently. But I still need to run it as and when required.
I am running Unbuntu 10.10 on a HTPC, and also XBMC. With some effort it worked ok, sounds, remote etc. Via systems>preferences I managed to add XBMC to the startup. It now starts when I start the PC. However it sort-of hijacks the PC, so the WiFi does not start among other things. Also I am no longer able to log into the desktop, so I am not able to emove XBMC from the start-up of the computer. If I exit XBMC I get to the log-in screen for the desktop, but when I log in it starts XBMC directly.
How can I remove it via the terminal? I cannot find a .config directory, any autostart, any .xsession, .xinitrc or anything else that looks like startup-script. How can I get access to my desktop again?
I'm unable to change startup programs. If I try and add or remove a program, any changes I have made seem to undo themselves. I suspect it might have something to do with being unable to save the session, but I really don't have a clue.
Just in case it makes a difference: I'm actually running Mint (Helena).
I get this Attention note when starting up to tell me that the system cannot handle video 1080 X 1024 which I am not using. I am using 1024 X 768. How can I get rid of this annoying little notice which slows down the start up considerable as it travel across the screen
How do I remove that annoying drum sound from the login screen.I went to PREFERENCES -> LOGIN SCREEN, but there are no tabs or boxes for sound. Only options to determine who I want to log in.I tried GCONF-EDITOR, and drilled down to /apps/gdm/simple-greeter/settings-manager-plugins/sound/active and unchecked the active box, rebooted, but it still plays that stupid sound. And the box is unchecked if I check it! I've tried the solutions in the forum and nothing seems to kill that annoying sound.I'm still on 9.10 right now, since 10.04 has a nasty screen flicker problem.
Somehow the -D option got tacked on to my sshd when I start up. How do I remove the -D option when sshd is started at boot? I'm guessing I need to edit something in /etc/init.d but not sure what. I checked System->Preferences->Startup Applications and the ssh server daemon isn't listed there. And since it is a command line option /etc/ssh/sshd_config is of no help.
Okay, two packages in question here: sshd and xrdp.
In the /etc/rc.d/rc5.d directory there is a K??sshd link, I'm not really sure why the default is to kill sshd in graphical mode, but it's there. I saw it coincidentally when I went to add an S??xrdp link so that I could have xrdp run when the computer starts. I restarted the computer, and of course, couldn't connect via my Windows Remote Desktop client. A quick ps -e | grep xrdp in a terminal window showed me that xrdp had not, in fact, started.
I hop back in to ??/rc5.d to see if I messed up creating my link and poof. there's no more S??xrdp link, furthermore, the K??sshd link that I had removed was back.
Okay, so Fedora doesn't like you messing with the init links manually... I can dig it, cause there's this nifty gui tool to manage startup items... I go in to that and add entries for sshd and xrdp, calling them via their init scripts so I can make sure everything plays nicely... then restart.
Oh, wait, still no xrdp or sshd running.
If I manually start these servers using their init scripts from a terminal they run fine, no issues, but I don't want to do that, and I think we can all agree that I should't have to. What am I doing wrong? What is the 'proper' way to add servers to the startup process and since entering runlevel 5 apparently kills sshd, how do I prevent that?