Ftp\http\Citadel don't work

Hello to all! I hope on your help.

Our site work ok… before Dallas rebooting….

After Rebooting Dallas today - our web site down…

1. After my linode back up - Start page become Citadel.

FTP doesn't work…

I look in to console and see that apache can't start becouse port 80 is busy.. after dialoge with support i stop citadel and start apache (not from fist time, after 2 reboots).

And Http become ok….

But ftp server still don't work…

In the log i see next:

Starting ftp server: proftpd - warning: unable to determine IP address of '69.164.193.239name1.mydomain.comname1'

  • error: no valid servers configured

  • Fatal: error processing configuration file '/etc/proftpd/proftpd.conf'

failed!

and some more info:

Starting amavisd: hostname: Unknown host

The value of variable $myhostname is "", but should have been

a fully qualified domain name; perhaps uname(3) did not provide such.

You must explicitly assign a FQDN of this host to variable $myhostname

in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's

network name!

(failed).

here is file hosts:

127.0.0.1 localhost.localdomain localhost

69.164.193.239 name1.mydomain.com name1

(real domain names are replaced)

More for this - now when i have reconfigure Citadel on other port (as support says) after trying start citadel i got next:

69:/# /etc/init.d/citadel restart

bash: /etc/init.d/citadel: No such file or directory

I hope on your help.

13 Replies

Even more! Support close my ticked with words:

"I'm sorry, but we cannot provide additional support for your configuration."

and linode now become unavaible every hour! even console didn't work! I need to reboot every hour to access to console!

Starting ftp server: proftpd - warning: unable to determine IP address of '69.164.193.239name1.mydomain.comname1'

Did you change the domain name or is that the real error? Perhaps a config file issue for proftpd - http://www.castaglia.org/proftpd/doc/co … O-DNS.html">http://www.castaglia.org/proftpd/doc/contrib/ProFTPD-mini-HOWTO-DNS.html?

I don't change anything - errors after rebooting Dallas. :-(

Now server fully unavaible again- even http…

What distro are you using? It sounds like it's misconfigured, cause 'hostname' should always return something like a host-name.

What Linode means is that they offered unmanaged services. If you're having a problem with your setup, it's up to you to fix it.

You could sum it up like this "You break it, you fix it."

Linode only ensures that you will have a reliable, stable environment. What you do inside the environment is outside the scope of their support.

I can understand it if i broke system myself. But system goes down without any changes from my side after rebooting of Dallas by Linode admins!

I open this topic to find help and to understand why ftp\mail servers didn't see my domain….

@Guspaz:

You could sum it up like this "You break it, you fix it."
But i break nothing! Server work well before "emergency reboot".

Not myself maded reboot but admins of Linode whole server!

And after this reboot settings become wrong?

Please better tell me if i remove current profile and create new - i will have clear system with default settings?

A reboot initiated by the host is no different then a reboot that you initiated by hand.

Your system was in a state of purgatory. It was living, but bound to die. (this is why you always reboot to ensure everything comes back up on its own)

If you decide to rebuild from scratch, make sure you reboot often in a controlled environment to make sure your init scripts start up in an expected order.

@adavin:

Please better tell me if i remove current profile and create new - i will have clear system with default settings?
Yes, if you delete the current profile (along with the associated disks images), and then re-deploy a new distro, you'll be back to square one.

You'll need to re-install and configure all of your apps, though. In your case, though, sounds like that may be a good opportunity for you to get things into a more stable state, though.

What is your native language?

My guess is Arabic.

Perhaps we can help better via Google Translate

mmm,… ??? just guessing here that adavin installed Citadel wrongly, that is - on top of Apache as if it were stand-alone, and/or perhaps wrongly chose 'option to integrate'? and thus when the linode rebooted "start page become [sic] Citadel". Somehow things kept running for adavin until the system rebooted. If so, then adavin, you're not too far from doing things correctly - but you will need to try again, …

This from the Linode Library Citadel install guide ::
> We assume you have followed the getting started guide as a prerequisite. We also assume you want to run Citadel by itself on this server, using port 80 or port 443 for browser-based access.

Please note: If you intend to install Citadel alongside a pre-existing web server package, do not select the option to integrate with that web server during setup. Select the option for "internal" when asked about web server integration, and be sure to specify unique ports for Citadel (such as 8080 for HTTP and 4343 for HTTPS).

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct