HOW TO: Setting up rails for shared hosting on a dedicated box. . .?
Hi All, As you may already know, A partner and I recently purchased a dedicated FreeBSD box. We're currently using Plesk (blech!) to manage client domains and such. I'm curious though as to what the best (most manageable) setup/configuration is for supporting Rails for each of our clients. Basically we want to be our own Shared Hosting Rails Provider (for lack of a more appropriate phrase) and need to figure out the best server configuration. Just a bit of an FYI, everything is already running on Apache2 so I'd need to share Apache2 among all programs (e.g. svn, rails, etc); as opposed to splitting tasks between Apache and Apache2. If you could point me in the right direction it would be most appreciated. Regards, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Properly managing SpamAssassin. . .
Hi All, I'm looking for a way to properly manage SpamAssassin after Plesk has wreaked havoc on the server. In the short term, we need to keep Plesk around for those that need the ease of use. However, it wants to keep resetting values, etc; meaning that since the Plesk license doesn't support SpamAssassin it won't allow us to use it and wants it to remain that way. If push comes to shove, I *will* blast Plesk. That said, I need to figure out the proper way to enable SpamAssassin and have Qscan work properly, circumventing the Plesk activites and licensing limitations. Does anyone have any quality insight into the most up-to-date means for accomplishing this? Regards, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Properly managing SpamAssassin. . .
Thanks, but there are two issues there: 1) I don't plan on keeping Plesk for more than a few months, and don't want to spend the effort/money just to undo/redo it later. 2) I want to manage it manually 100% from the start That said, are there any suggestions as to how to accomplish what I've requested? Regards, Michael On Jul 18, 2007, at 11:28 AM, Daniel Anson wrote: You can buy a spamassasin liscense from plesk. I would suggest that. Daniel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Williams Sent: Wednesday, July 18, 2007 10:05 AM To: freebsd-stable@freebsd.org Subject: Properly managing SpamAssassin. . . Hi All, I'm looking for a way to properly manage SpamAssassin after Plesk has wreaked havoc on the server. In the short term, we need to keep Plesk around for those that need the ease of use. However, it wants to keep resetting values, etc; meaning that since the Plesk license doesn't support SpamAssassin it won't allow us to use it and wants it to remain that way. If push comes to shove, I *will* blast Plesk. That said, I need to figure out the proper way to enable SpamAssassin and have Qscan work properly, circumventing the Plesk activites and licensing limitations. Does anyone have any quality insight into the most up-to-date means for accomplishing this? Regards, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Properly managing SpamAssassin. . .
Kevin, Thanks. I have no problem with that at all. Can you recommend any quality, modular (redundant I know) jailing techniques (e.g. directory structures, user levels, permissions, etc)? Regards, Michael On Jul 18, 2007, at 11:34 AM, Kevin K. wrote: Managing plesk usually means that you really have to hand over your server (or the jail that plesk creates) to plesk itself. I've hacked and mangled plesk installations in order to merge other technologies and custom solutions that I personally preferred -- and in the end I concluded that it caused more headaches than it was worth. As of plesk 8.1 I believe it creates its installation in a jailed environment, so perhaps adding another jail to handle all the services you don't want to purchase through plesk (i.e. spamassassin, clamav, or whatever elese there is) may be the best way. That's my 0.2, perhaps someone else has a better solution though. Again, changing or hacking a plesk installation is not a good idea, considering their windows update style of submitting upgrades and patches. Hope it helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Williams Sent: Wednesday, July 18, 2007 11:05 AM To: freebsd-stable@freebsd.org Subject: Properly managing SpamAssassin. . . Hi All, I'm looking for a way to properly manage SpamAssassin after Plesk has wreaked havoc on the server. In the short term, we need to keep Plesk around for those that need the ease of use. However, it wants to keep resetting values, etc; meaning that since the Plesk license doesn't support SpamAssassin it won't allow us to use it and wants it to remain that way. If push comes to shove, I *will* blast Plesk. That said, I need to figure out the proper way to enable SpamAssassin and have Qscan work properly, circumventing the Plesk activites and licensing limitations. Does anyone have any quality insight into the most up-to-date means for accomplishing this? Regards, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- [EMAIL PROTECTED] __ NOD32 2404 (20070717) Information __ This message was checked by NOD32 antivirus system. http://www.eset.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
Alright all, First and foremost, you ladies and gents have been *amazingly* responsive and helpful; for that I thank you. We've gotten the root issue resolved. I fiiinally spoke to someone that was familiar enough to log a request for good ole single user mode to simply blast the root password. I had root access within 15 minutes. It turns out that even the root password they had on hand was wrong so they were forced to resolve the issue. I am now all-powerful. . .well on that server anyway. ;) I will likely be keeping Plesk around in the short term in order to allow lower admins to easily set up a few clients, but its days are numbered. Thanks again for all your input/help. Best Regards, Michael On Jul 17, 2007, at 5:54 AM, Julian H. Stacey wrote: Norberto Meijome wrote: Michael Williams [EMAIL PROTECTED] wrote: I'm going to call one more time today. If I get no better assistance, I will seek out a different company. If you all have any recommendations let me know. http://bsn.com : Small v. flexible BSD ISP server hosting provision. Sparcs available too. http://consol.de Bigger. Both host http:// berklix.org servers. Search the archives for discussions on FreeBSD Hosting. http://www.freebsd.org/commercial/isp.html -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http:// berklix.com Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
No, I don't necessarily need Plesk; although we will be selling
hosting. It simply came with the default configuration for the
server. My plan is to manage most everything from the Unix shell. I
just figured I might find a morsel inside Plesk somewhere for
enabling root access. FYI, logging in as admin didn't work. Any
other suggestions?
Regards,
Michael
On Jul 16, 2007, at 2:04 AM, Norberto Meijome wrote:
On Sun, 15 Jul 2007 21:35:52 -0400
Michael Williams [EMAIL PROTECTED] wrote:
. Anyway, if
you can think of *any* solution to this issue, it'd be much
appreciated. For the record, the following are my Plesk Control
Panel offerings for SSH login:
Hi Michael,
you hadn't mentioned you are using Plesk :)
/bin/sh
/bin/csh
/bin/tcsh
/bin/sh(chrooted)
/usr/local/bin/bash
Make sure you choose /bin/sh (NOT CHROOTED).
also, if you are SSHing to your server via an account created with
Plesk, which can creates chroots environments for those accounts.
Try ssh as admin with your plesk password straight into the box.
If I may ask, do you need Plesk? For some users and situations, it
may be a good tool ( shared webhosting with many accounts ), and
even in those cases I've found it to be more problem that is worth
it, as it adds so many layers of scripts and software that you are
mostly stuck with whatever is compatible with Plesk, or hacks
around that (either way, not ideal). YMMV, of course.
B
_
{Beto|Norberto|Numard} Meijome
Egotism is the anesthetic that dulls the pain of stupidity.
Frank Leahy
I speak for myself, not my employer. Contents may be hot. Slippery
when wet. Reading disclaimers makes you go blind. Writing them is
worse. You have been Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
Tom, Again, Plesk just came with the server config we asked for. We didn't ask for Plesk, we *asked* for the specific hardware. Plesk was free. *rolls eyes* Regards, Michael On Jul 16, 2007, at 3:17 AM, Tom Samplonius wrote: - Michael Williams [EMAIL PROTECTED] wrote: No, I don't necessarily need Plesk; although we will be selling hosting. It simply came with the default configuration for the server. My plan is to manage most everything from the Unix shell. I just figured I might find a morsel inside Plesk somewhere for enabling root access. FYI, logging in as admin didn't work. Any other suggestions? You are probably better off just asking the hosting company for the password. You need the root password, and you need to have an account that is a member of the wheel group (use groups when you ssh to see if your account is ok). They might have flagged you as a newbie, and think you are better off inside the padded confines of Plesk. I work at a hosting company, and a whole bunch of our dedicated server customers are in over their heads with their servers as it is. Given that you asked for Plesk, and are now asking for root, they are probably has made them worried that the next call from you will be that you deleted / etc, and your server won't boot anymore. If you are planning to do any admin via ssh with root, you will not want Plesk. Plesk manages all of your software installs. Plesk includes Plesk specific versions of Apache, PHP, and MySQL. All patches and updates can only come from SWSoft, or the Plesk universe will crash. And Plesk ties you to a specific FreeBSD version too. Plesk versions lag big time for FreeBSD. But on the other hand, it is big GUI thing, and people like it. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
Also, if you follow the thread, you'll note that we've asked for root several times. Yet, they keep asking us for the root password so that they can make changes. A lot of canned responses, etc. Regards, Michael On Jul 16, 2007, at 3:17 AM, Tom Samplonius wrote: - Michael Williams [EMAIL PROTECTED] wrote: No, I don't necessarily need Plesk; although we will be selling hosting. It simply came with the default configuration for the server. My plan is to manage most everything from the Unix shell. I just figured I might find a morsel inside Plesk somewhere for enabling root access. FYI, logging in as admin didn't work. Any other suggestions? You are probably better off just asking the hosting company for the password. You need the root password, and you need to have an account that is a member of the wheel group (use groups when you ssh to see if your account is ok). They might have flagged you as a newbie, and think you are better off inside the padded confines of Plesk. I work at a hosting company, and a whole bunch of our dedicated server customers are in over their heads with their servers as it is. Given that you asked for Plesk, and are now asking for root, they are probably has made them worried that the next call from you will be that you deleted / etc, and your server won't boot anymore. If you are planning to do any admin via ssh with root, you will not want Plesk. Plesk manages all of your software installs. Plesk includes Plesk specific versions of Apache, PHP, and MySQL. All patches and updates can only come from SWSoft, or the Plesk universe will crash. And Plesk ties you to a specific FreeBSD version too. Plesk versions lag big time for FreeBSD. But on the other hand, it is big GUI thing, and people like it. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
First, the output of the grep is: root:*:0:0:Charlie :/root:/bin/csh toor:*:0:0:Bourne-again Superuser:/root: daemon:*:1:1:Owner of many system processes:/root:/usr/sbin/nologin . . .that said, the Plesk Module Loader only allows for .tgz and .tbz files and is anal about them being of a module format, whatever structure may be. I've tried what I thought were appropriate modules, and it rejected them saying they were not true modules. I'm going to call one more time today. If I get no better assistance, I will seek out a different company. If you all have any recommendations let me know. Obviously, the best solution would be to have my ISP set me up with a static IP and massive amounts of bandwidth. But, seeing as how that's at least a good 30 years off. . . Regards, Michael On Jul 16, 2007, at 11:03 AM, Vince wrote: For most versions of plesk i've come across (I look after a load of linux servers with it installed,) if you have the plesk admin then you have root. Look for the modules option, then look for the add modules, this should let you upload a shell script which is then run as root (horribly insecure but thats plesk, and if you fiddle with their setting enough you can change the css of the webapp not to display the page) If this is the same on FreeBSD as on linux you can create a new UID 0 user if need be using pw in a shell script, or you can put a ssh public key in to roots authorized_keys file. I'd definitely advise you get plesk removed if you intend to administrate the box by hand though. If thats no help, when you log into the box by ssh, what is the output of grep root /etc/passwd it should be something like root:*:0:0:Charlie :/root:/bin/csh if not then they have renamed/removed root so try looking in /etc/ passwd for a user with uid of 0 (third field.) This should at least get you a username to ask their support about. If they have actually removed the root user your a bit stuffed and Hope some of thats some help. Vince Michael Williams wrote: Tom, Again, Plesk just came with the server config we asked for. We didn't ask for Plesk, we *asked* for the specific hardware. Plesk was free. *rolls eyes* Regards, Michael On Jul 16, 2007, at 3:17 AM, Tom Samplonius wrote: - Michael Williams [EMAIL PROTECTED] wrote: No, I don't necessarily need Plesk; although we will be selling hosting. It simply came with the default configuration for the server. My plan is to manage most everything from the Unix shell. I just figured I might find a morsel inside Plesk somewhere for enabling root access. FYI, logging in as admin didn't work. Any other suggestions? You are probably better off just asking the hosting company for the password. You need the root password, and you need to have an account that is a member of the wheel group (use groups when you ssh to see if your account is ok). They might have flagged you as a newbie, and think you are better off inside the padded confines of Plesk. I work at a hosting company, and a whole bunch of our dedicated server customers are in over their heads with their servers as it is. Given that you asked for Plesk, and are now asking for root, they are probably has made them worried that the next call from you will be that you deleted /etc, and your server won't boot anymore. If you are planning to do any admin via ssh with root, you will not want Plesk. Plesk manages all of your software installs. Plesk includes Plesk specific versions of Apache, PHP, and MySQL. All patches and updates can only come from SWSoft, or the Plesk universe will crash. And Plesk ties you to a specific FreeBSD version too. Plesk versions lag big time for FreeBSD. But on the other hand, it is big GUI thing, and people like it. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HOW TO: Enabling root on a new server?
Well, that's just it. As with many large corporations, there appear to be a great many degrees of separation between the folks we're talking to and the folks we *need* to talk to. That aside, we've been assured that it is absolutely our own dedicated server. (It'd better be as we just upgraded from Virtual to Dedicated hardware). I'm at wits end regarding this issue though. I'm tempted to simply go back to hosted solutions instead of dealing with this. Anyway, if you can think of *any* solution to this issue, it'd be much appreciated. For the record, the following are my Plesk Control Panel offerings for SSH login: /bin/sh /bin/csh /bin/tcsh /bin/sh(chrooted) /usr/local/bin/bash . . .I've tried each, to no avail. I'm absolutely 100% lost. Regards, Michael On Jul 13, 2007, at 8:00 AM, [EMAIL PROTECTED] wrote: Message: 16 Date: Thu, 12 Jul 2007 20:35:52 -0700 From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: HOW TO: Enabling root on a new server? To: Michael Williams [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii On Thu, Jul 12, 2007 at 11:06:07PM -0400, Michael Williams wrote: I recently purchased a co-located server from Cedant and need to enable the root user. It's running FreeBSD 6.1. Currently there appears to be no root user enabled on the server. I can't even su to root. I've tried using pw to add my user to wheel but I receive a warning informing me that I must be root to even do such a thing. You can see my quandary. Please advise. FreeBSD, out-of-the-box, definitely includes user root, and there is no password (unless during the installation you choose to set one). This sounds like a question you should be talking to Cedant/your provider about. What you purchased may not be a real co-located box that's personally dedicated to you -- it may be something shared with other people, and something that Cedant maintains. This is purely speculative on my part, because I know nothing about their services. But this really does sound like something specific to their servers. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HOW TO: Enabling root on a new server?
Hi All, I recently purchased a co-located server from Cedant and need to enable the root user. It's running FreeBSD 6.1. Currently there appears to be no root user enabled on the server. I can't even su to root. I've tried using pw to add my user to wheel but I receive a warning informing me that I must be root to even do such a thing. You can see my quandary. Please advise. Regards, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
