Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Feature Requests

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 13th March 2008, 15:55
TauTau TauTau is offline
Member
 
Join Date: Oct 2007
Posts: 33
Thanks: 1
Thanked 0 Times in 0 Posts
Default Escalate Errors from httpd -t to Browser

Hi,

I had several occasions now, where a problem only had the reason, that the vhosts file would not be accepted. If I hadn't checked the log, I would never have known why my vhosts config wasn't updated anymore. It would be helpful, if any error that results in a old vhosts being used, would be escalated/written/popuped somewhere visibly. Those Errors usually result from the httpd -t ISPConfig makes, and I guess it could be possible to pipe that output to some file that is displayed then.
Reply With Quote
Sponsored Links
  #2  
Old 14th March 2008, 10:17
Ben Ben is offline
Moderator
 
Join Date: Jul 2006
Posts: 1,029
Thanks: 7
Thanked 62 Times in 56 Posts
Default

Maybe a more quick solution could be to just display the ispconfig.log in the webinterface, but then you would still have to check this log after changing settings.
But for my understanding the update process is an asynchronous one, so that there won't be a possibility to directly feedback to the webinterface after submitting the new data.

Another thing is how to find a more general solution, e.g. an enduser won't be really interested in seeing these errors...
Reply With Quote
  #3  
Old 14th March 2008, 10:36
TauTau TauTau is offline
Member
 
Join Date: Oct 2007
Posts: 33
Thanks: 1
Thanked 0 Times in 0 Posts
 
Default

yeah, I always forget that there are endusers working with this But of course it would be important for them to know, that no changes are applied. And to inform the admin, they should have a way to copy&paste the relevant error from httpd -t. Currently even I can't see the error in the log, I have to copy the "broken" config there, run httpd -t manually and check the error.

Thinking about bigger sites, where users can (can they?) enter Apache directives, they could break the system for everyone else...

Just a thought, I'm the only user of ISPconfig here, and *I* know now about the importance of checking that log
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Revisit: ISPConfig, httpd and wierd logging errors zetnsh Installation/Configuration 2 1st February 2008 21:18
Apache / httpd restart / startup failed without errors Aldert Server Operation 11 30th January 2008 18:11
httpd syntax seems to contain errors, reloading with old configuration dimitar Installation/Configuration 3 2nd January 2008 12:54
Install Errors DarkLord00 Installation/Configuration 12 25th February 2007 18:49
MaxClients set to appropriate level, but ISPconfig is crashing from it (I think) bpmee Server Operation 6 11th January 2007 20:29


All times are GMT +2. The time now is 22:54.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.