Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Preface: I was thrown into setting up a trouble ticket system (http://www.troubleticketexpress.com/) without any previous knowledge of web servers. There may be some incorrect terminology used as I am a giant n00b.
I am trying to install the above trouble ticket system on a development machine running a fresh installation of Apache 5.5. I have uploaded all of the files to a directory that I created: /var/www/TT
httpd.conf has the line DocumentRoot /var/www which is the directory that I wish to use as the default for the time being. When I try to view a file that is in /var/www Firefox returns a "Failed to connect" error. I get similar errors with other browsers.
I can ping the URL all day without a problem and permission for the directory and any files I've tried viewing (.txt .html and .cgi) are set to 755. This seems like something fairly simple, my trouble is that I just don't know enough about Apache (or other something else?) to troubleshoot.
I've uploaded files to var/www and var/www/TT and haven't been able to view any of them at Your_URL or Your_URL/TT
For example: I uploaded index.html to var/www but it did not display when I went to either Your_URL or Your_URL/index.html. I've also tried just viewing a text file at var/www/hello.txt and had the same problem.
AuroraCA: After looking a little more, I found some release notes that says it is Apache Tomcat 5.5. Now that I'm thinking about this more. I'm not even certain this is running on Linux, so I'll have to look into that also.
Quote:
Did you change the owner and/or group of the directory and files to reflect the default apache user, i.e. apache, www-data, nobody, etc.?
Doubtful. The owner is "root" which is me. Could you explain how I change it to reflect the default apache user?
Distribution: Ubuntu, Slackware, Gentoo, Fedora, Red Hat, Puppy Linux
Posts: 370
Rep:
I am glad that you don't work in a hospital. I cannot believe that you don't know a thing about the computer or operating system and you are thrown into server administration to try to set up a new system. I would suggest that you get an elementary book on Linux or spend some time learning Linux and learning to use Google because a Linux Server should not be managed or administered by learning in a help forum. There is way too much that you don't know.
For instance, the most elementary task in Linux is changing owner and group of files and directories. If you don't have that basic facility then you are in way over your head.
Seek professional administration help as there is a lot that you can screw up if you don't know what you are doing. You don't even know what questions to ask even know how to provide basic information about your system.
Total-MAdMaN: Thank you, that is definitely a step in the right direction.
AuroraCA: Ok I'll go learn how to use Google and leave you alone.
**edit**
Sorry to be fresh. I know I'm over my head and was just looking for any help at all. This is basically a "get it done now and learn what you did later" type of situation. You're being honest and telling me that it's not possible. I appreciate the honesty.
Last edited by orangeghost; 10-24-2008 at 12:28 PM.
Distribution: Ubuntu, Slackware, Gentoo, Fedora, Red Hat, Puppy Linux
Posts: 370
Rep:
orangeghost
I am sorry that you took my post to mean "don't bother me". It could not be further from the truth since if you look at assistance I've provided here in the past I believe that I've shown a willingness to help and explain solutions to Linux problems for Linux newbies/novices. I did not mean that you should learn to Google to fix this problem but that you should use Google to help you learn Linux. It seems you know nothing of the basic structure of a Linux/Apache server or even basic Linux commands.
I am just fearful that you will do something that will get you deeper into a hole because you do not understand the implications of how changing one thing in your system can break other things. You may give limited facts based upon your limited Linux knowledge which will elicit an answer which may make your situation worse. If you were just trying to get your movie player to work or create a backup script then that would be a different matter. You are apparently using a live company server which is used for productivity and development which could cost your company money to recreate if it becomes corrupted.
Sometimes a simple answer is not your solution.
I wish you well and still believe that you and/or your company should find an experienced system administrator to maintain your live systems.
@orangeghost: I don't want to scold you (so won't), but it is pretty irresponsible of your employer to foist this on you. I suppose that is another story. At the very least, I would be sure you're managing your boss's expectations -- s/he needs to understand that there is a big learning curve associated with you taking on a new OS and new application stack. There are expert contractors who get paid big $$ to do what your employer decided you should do...
Anyway, assuming you can't get out of this situation, I would suggest the following approach:
Get yourself a book on Linux for beginners. Try to buy something that targets your OS and version. Read it and walk through the practice exercises.
Acquire a test server at work that you can play on and learn on.
Do not touch the production server until you know what you're doing!!
Insist that your employer send you to formal training to get you up to speed quickly. I recommend Red Hat's RHCT track to get you started. (I am not a Red Hat employee, and I don't get paid to suggest that.)
Get back to your test box and play some more - this will be an iterative process that could take months or longer.
When you're feeling comfortable with the OS and the app stack, set up your test environment as close as possible to your production environment.
Establish a change control process, a backup process, and a testing process.
Make changes to your test server and test them.
Make changes to your prod server and test them.
Approach employer; tactfully, but firmly, suggest that your salary gets more inline with your new responsibilities.
You folks are really great. I apologize for that last post. It was frustration with the situation and you are just trying to help me. You didn't deserve that. I should have said before that this is strictly a learning task. The only thing I need to do is install the trouble ticket system. I'm not touching anything that is live.
The situation is this: It is a development server that only I have access to. There is no way to damage the hardware doing what I'm doing, so there's no potential risk of money loss (other than my time). As far as why I'm working on this, my employer wants me to begin to learn server administration so basically said "Here, see if you can make this work, if not, we'll have someone who knows how to do it take care of everything."
I'll take your advice though, and have someone who knows what they're doing take on this project. Then I'll get a book and see where that takes me.
Distribution: Ubuntu, Slackware, Gentoo, Fedora, Red Hat, Puppy Linux
Posts: 370
Rep:
That puts things in an entirely different light. How did the instructions that Total-MAdMaN gave a few posts back work our for you?
When you ask for advice always specify which Linux distribution you are using and what version. This is very important since many distributions have different ways of implementing standard packages such as Apache or networking. Knowing the distribution and version will avoid confusion about the best advice to give. Different distributions use different default Apache users.
Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12etch2) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed May 9 23:03:12 UTC 2007
Although I read that "Catting /proc/version or uname will only show you information that has been set for compile into the kernel."
chown -R <user>:<group> <directory>
I changed the owner and group to that which Apache is running as (www-data). Still have the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.