InterWorx 1.9.0 Release

[IWorx-Paul]

We're pleased to announce the release InterWorx-CP 1.9.0.

Your InterWorx-CP servers will automatically update within 24 hours if you have automatic updates enabled (the default). If you want to initate the upgrade yourself, we recommend logging into the server as root and running the following command:

yum update

-- New Features --

* Spamassassin / ClamAV Suppport (SPAM / Virus filtering)

IWorx-CP can now filter viruses / spam at both the MDA and MTA levels.
There are global settings that apply to the server as a whole and
per-domain settings for each SiteWorx account on the server. This is
all fully configurable via the software. Virus definition updates are also automatic.

* Multi-Language Support

IWorx-CP now ships with English and French languages and more languages can easily be added via the NodeWorx interface. Langauges can be set on a
per-user basis.

* AWStats / Analog Support

IWorx-CP now ships with both AWStats and Analog stats in addition to the
realtime and webalizer stats that existed in pre-1.9.0 releases.

* SiteWorx Backup / Restore

It is now possible to backup a SiteWorx account with all of its
settings, files, databases etc entact and restore this account on
another IWorx-CP server. The NodeWorx user can backup multiple SiteWorx
accounts at once from the NodeWorx console.

The backup is granular, with sql databses, email and web content all
selectable in the backup process.

* CPanel Import

IWorx-CP now supports the imporation of any CPanel backup file. Simply
upload the CPanel backup file and IWorx-CP will import all settings,
files, databases etc into a new SiteWorx account.

* DNS TXT Record Support

To comply with the SPF method of spam prevention IWorx-CP now supports
the TXT DNS record.

* Wildcard DNS Support

IWorx-CP now supports wildcard DNS entries (*.domain.com)

* SSL Certificates Now Support "Chain" certs

- New Supported Platforms:

* Fedora Core 3
* CentOS 3.4
* RedHat Enterprise Linux 4.x

- Copy-to option for e-mail boxes
E-mail boxes can now be configured with a "copy to" address.

- Webmail Upgrade

The default webmail system (Horde) got a major upgrade to the version
3.x.x line of their product. We also bundle the latest squirrelmail
webmail software as well.

- phpMyAdmin Upgrade

phpMyAdmin was upgraded to the latest stable release.

Thanks for your continued support of InterWorx-CP!
Paul

[Lost]

Looks great guys.. Lots of new toys to play with now!

I gather the 1.9.0 release is responsible for the new users (clamav, spamd, simscan) and groups that have been created on my server.


P.S. Thanks for adding the TXT record support so I can enable sender Policy framework! :)

[IWorx-Paul]

I gather the 1.9.0 release is responsible for the new users (clamav, spamd, simscan) and groups that have been created on my server. Yes, that's correct

[Justec]

Are there any scheduled ClamAV scans of the server itself?

...and if not what is the best way to setup the cron for that?

Thanks,

[RWF]

I find it especially nice to see AWStats incorporated, however is it just me, because I can't seem to get AWStats or Analog Stats to do anything.

The page "only" shows a "Date" form containing no links on any dates. Switching to Monthly is the exact same thing.

[CMI]

I find it especially nice to see AWStats incorporated, however is it just me, because I can't seem to get AWStats or Analog Stats to do anything.

The page "only" shows a "Date" form containing no links on any dates. Switching to Monthly is the exact same thing.

Perhaps stats haven't been calculated yet? AWStats didn't have anything on our box right away. Just checking, there are stats starting on the 22nd.

[RWF]

I assumed, and had very much hoped, that AwStats and Analog stats was "just" two more ways to crunch the same, read already existing log files.

[Justec]

I assumed, and had very much hoped, that AwStats and Analog stats was "just" two more ways to crunch the same, read already existing log files.
The stats program hasn't run on your box yet. Mine runs early in the morning so I would check tomorrow after 9am.

Also, it does not backlog, the new stats will start from the day you have upgraded.

[IWorx-Paul]

RWF: Unfortunately it isn't practical to keep all previous log files, once stats are calculated for the day the raw log files are purged.

Justec: No, there's no server wide scan set up - and I haven't given much thought to setting this up, but the first step would be to set up clamd to run as root - since it will need to be able to access all fiels on the server. You do this by editing /etc/clamd.conf and commenting out the line:

User clamav

Then restart clamd:

# service clamd restart

Then, you just run the program clamdscan in the directory you want to scan, details are in the clamdscan man page.

# man clamdscan

[Justec]

For the second time since my upgrade my webserver has turned off. When I mean web server I am referring to just Apache, the server itself is up and running fine with all other services.

I think it has something to do with the stats which run in the morning. I have not changed anything apache config files or added any accounts since the upgrade. It is weird that sometimes it's fine, 4 out of the 6 days I have had 1.9 the webserer was still up after the stats.

I guess it could be unrelated, but that fact that it happens around the same time as the stats is why I'm thinking it is linked somehow.


In the Log I got a bunch of these warnings before it shutdown:

[Mon Feb 28 08:07:39 2005] [warn] child process 25645 still did not exit, sending a SIGTERM
[Mon Feb 28 08:07:39 2005] [warn] child process 25646 still did not exit, sending a SIGTERM


Any ideas?

Thanks

[juangake]

Just a post to congratulate Interworx team for this release. Nifty and nice new features and smooth patching :)

Keep the good work!

Juan
www.sowsl.com

[JayBaen]

Since the upgrade, I'm getting a lot of these messaages when trying to browse various siteworx accounts from within the Nodeworx interface:

InterWorx Oops: /home/interworx/include/nodeworx/IPAddress.php (130):


----- DEBUG STACKTRACE BEGIN -----
/home/interworx/include/debug.php debug_printstacktrace (182)
0 debug_assert (0)
/home/interworx/include/nodeworx/IPAddress.php assert (130)
/home/interworx/include/nodeworx/IPAddress.php _populate (85)
/home/interworx/include/nodeworx/IPAddress.php _populateip (63)
/home/interworx/include/siteworx/SiteWorx.php ipaddress (1649)
/home/interworx/include/siteworx/SiteWorx.php getiptype (349)
/home/interworx/siteworx/html/siteworx.php getsmarty (45)
/home/interworx/siteworx/html/siteworx.php _il_exec (2)
----- DEBUG STACKTRACE END -----



----- DEBUG STACKTRACE BEGIN -----
/home/interworx/include/debug.php debug_printstacktrace (127)
/home/interworx/include/database.php debug_die (62)
/home/interworx/include/database.php db_query (117)
/home/interworx/include/nodeworx/IPAddress.php db_object (142)
/home/interworx/include/nodeworx/IPAddress.php _populate (85)
/home/interworx/include/nodeworx/IPAddress.php _populateip (63)
/home/interworx/include/siteworx/SiteWorx.php ipaddress (1649)
/home/interworx/include/siteworx/SiteWorx.php getiptype (349)
/home/interworx/siteworx/html/siteworx.php getsmarty (45)
/home/interworx/siteworx/html/siteworx.php _il_exec (2)
----- DEBUG STACKTRACE END -----

/home/interworx/include/database.php(62): DB Error: syntax error

**edit** I also seem to be missing the last 2 IPs on the box in the IP Management section ... (these things seem related).

Help?

JB

[PaulK]

Congrats on the 1.9 release. When I select an account plan from the popup in the new account page, I get a javascript dialog that simply says "Hi". I assume this is some debug code that slipped through to release?

[IWorx-Paul]

JB: Are those two IPs still bound to the server (listed in ifconfig output). It'd probably be best if you could open a support ticket to better track this issue.

PaulK: Which theme are you using?

Paul

[IWorx-Paul]

PaulK: I'm not sure which section you're describing. Do you mean "drop down" instead of "pop up"?

[JayBaen]

I would *assume* they are as the web sites that are bound to them are still responding correctly ...

*BUT*

/sbin/ifconfig reveals:

eth0
and eth0:1-9 are bound

... with the execption of eth0:7 -- this one (and it's associated IP) are missing, but aren't the IPs in question from Nodeworx.

Help?

JB

[IWorx-Paul]

JB, try running the /home/interworx/cron/ip.pex --sync
script.

If that doesn't help, open a support ticket w/ your server login info and we'll check it out.

Paul

[JayBaen]

Good good ... the script *did* re-sync them. Yea.

FYI, when they re-appeared, the IPs in question showed up as "dedicated," even though I could view the 4 domains bound to the IP via the hyperlink. Once I re-chose "shared," I received the "4 Domains" indicator by the IP (which was missing).

As for the other issue of the missing eth0:7 -- maybe I've just never noticed this before (and/or never had a need to look). Obviously, I'd like to have access to that IP. I know it's not your issue that it doesn't seem to exist at the box level currently -- but I'd appreciate it if you could throw me a pearl. Any thoughts as how to remedy this?

**edit** .. nm, a reboot re-bound it. Thx for the help.

JB

[JayBaen]

OH .. new problem.

Any of the 4 domains that resolved to the once-missing IP now all pull the SAME web site after the re-sync .. !

?

Meaning, DNS resolves the IP addy fine, goes to the box and pulls the same web site for all 4 domains.

Thoughts?

**edit** moving to support ticket ...

JB

[Justec]

It happen again today, I had to start up Apache manually :(

No one else is having this problem?

----------
Another thing I noticed:

Update was done at 8:22am this morning (Mar-1), the same time apache shut down so maybe it isn't the Stats, but the update.

It shut down yesterday at 8:07am (Feb-28). There was no update on the 28th, but there was an update on the 27th. Apache did not shut down on the 27th which was good, but the update that ran on the 27th ran at 8:07am which happen to be the same time apache shut down yesterday morning (Feb-28th).

Any ideas?

[JayBaen]

A head's up ...

After last night's update, I had to reboot the box via SSH to get any services to respond.

JB

[IWorx-Chris]

JB, Could you elaborate? Were they 'off'? What happened when you tried to restart them either via NodeWorx or ssh? Any other info you can provide?

Thanks,

Chris

[JayBaen]

Services displayed as "on" and were able to be restarted manually -- but with no result (meaning, webs, email and FTP still unresponsive).

A reboot brought things back to life.

On a not-so-side note, I've got an open ticket with the NOC to check on the status of the network card of that box, as it's the same one randomly dropping the IP interfaces. It's very possilbe these things could be related.

JB

[Justec]

This is similar to my HTTPS not working yesterday, doing a netstat showed that apache was just not listening on port 443, doing a reboot fixed it, this was after an update yesterday morning 3/1 (NOT today).

The update was a bunch of XFree86 stuff.

[RWF]

Ok first I was very happy that AWStats was offered as an alternative, however a bit dissaopinted that it where not able to show previous days (time), using already stored log files.

Anyways that I can live with, but that a process called "awstats.pl" is eating up my most of my servers CPU time, for approximately two hours every afternoon, cpu utilization goes from 10% to 80%, I am not sure I can or will live with.

How do I turn off AwStats?

[IWorx-Chris]

How do I turn off AwStats?


Edit /home/interworx/iworx.ini

Search for:


[stats.awstats]
enabled="1"


change to:


[stats.awstats]
enabled="0"


Chris

[RWF]

Thanks Chris!

Anyone else seeing this cpu usage?

Is that function really so CPU intensive, or is it just because my sites are quite busy with visitors?

[RWF]

Ok I opened the file via SSH and edited with Notepad. However there where all these "funky" characters in Notepad instead line breaks. This I ignored found the text, edited, saved, and uploaded. Then Interworx would not work.

Then I opened the file again, in Notepad, copied and pasted into Word, and back into Notepad, so the funky line breaks where treated in Notepad as regular line breaks, everything was not on the same line, uploaded, and Interworx still does not work?

Should that ini file not be a regular text file?

[IWorx-Chris]

It's cpu intensive RWF, no doubt about it. All of our boxes see the same.

Chris

[IWorx-Chris]

I wouldn't copy it back / forth RWF even while pasting just to keep errors to a minimum. Just edit it in place with emacs, vi, pico etc.

Chris

[Justec]

Ok I opened the file via SSH and edited with Notepad. However there where all these "funky" characters in Notepad instead line breaks. This I ignored found the text, edited, saved, and uploaded. Then Interworx would not work.

Then I opened the file again, in Notepad, copied and pasted into Word, and back into Notepad, so the funky line breaks where treated in Notepad as regular line breaks, everything was not on the same line, uploaded, and Interworx still does not work?

Should that ini file not be a regular text file?

You should just edit the files with SSH using the VI editor. If you download them to windows you can use it with notepad i think (not word or wordpad).

As to the stats themselves, mine run at 8.30 ish in the morning at the same time as my update and i have about 99% CPU load for 5 mins or so.

I would really like to know how we can adjust the times of the update and stats run at.

[RWF]

I wouldn't copy it back / forth RWF even while pasting just to keep errors to a minimum. Just edit it in place with emacs, vi, pico etc.

Chris


This is how I 've done it succesful before with fx. webalizer.conf. Anways too late for advising not to copy and paste, and I tried just downloading and editing the file first.

Now the file is apparently messed up, and I do not have any of the apps you talk about. How do I fix the file? It seems to be in plain text format, but is apparently not understood by Interworx.

[RWF]

You should just edit the files with SSH using the VI editor. If you download them to windows you can use it with notepad i think (not word or wordpad).

As to the stats themselves, mine run at 8.30 ish in the morning at the same time as my update and i have about 99% CPU load for 5 mins or so.

I would really like to know how we can adjust the times of the update and stats run at.


Thanks for your advise, however my SSH program (SSH Secure Shell v.3.1.0) does not have anything called VI-Editor, never seen it, and I did a search in the help section.


And I did open the ini file in Notepad, but like I said everything was on one line with funky characters between was should be lines.

[RWF]

This is first text line of the error text I get now when trying to go to Interworx.

Warning: parse_ini_file(): Cannot open '/home/interworx/iworx.ini' for reading in /home/interworx/include/INIConfig.php on line 44


I guess I have to open a support ticket about this. I just can't believe that this file is not plain text that could be understood by Notepad.

[IWorx-Paul]

RWF, the permissions are almost certainly the issue. Log into the server as root and run the following command:

chown iworx.iworx /home/interworx/iworx.ini
chmod 600 /home/interworx/iworx.ini

Paul

[Justec]

From the shell you just type "vi filename" and it will open the editor.
It is not with your SSH program it is in Linux and almost every Linux distro has
VI.

Another good practice is to make a backup of any config file before you edit it so if you mess up you can copy it back over from the backup file.

cp interworx.ini interworx.ini.bak_3-2-05

then if you mess up you just cp interworx.ini.back_3-2-05 interworx.ini

[RWF]

RWF, the permissions are almost certainly the issue. Log into the server as root and run the following command:

chown iworx.iworx /home/interworx/iworx.ini
chmod 600 /home/interworx/iworx.ini

Paul


Thanks! Actually the first line was enough to get thing to work again :)

[IWorx-Socheat]

I guess I have to open a support ticket about this. I just can't believe that this file is not plain text that could be understood by Notepad.

Though the issue was fixing the permissions, just wanted to make another comment. While the file is plain text, and is understood by Notepad, Unix and Windows use different characters to represent a newline. This is what caused the "funky" characters and everything to appear on a single line in Notepad.

[kipper3d]

Good morning,

Appears 1.9 was released 02-27-2005. One of my servers that set to auto update, never updated. I even refreshed and ran install in the updates section in nodeworx, but still nothing. I havent tried yum update yet. Wondering if there was a reason it wasn't updated.

Other problem, is my AMD64 server, interworx appears to be broken. Perhaps needs to be recompiled for the update?

Thanks,

[pascal]

Hello ;)

Just a question relating to the 1.9 release :

- Did you upgrade the "create siteworx account" parameters' API to have the language option, spam option, ... ?


About the bandwidth limit and the burstable option (not sure it is related to the 1.9) :

- when a user exceeds the limit of bandwidth there is no mail alarm sent to the administrator of the box. It's a shame, as I can't check all account every days and I can't force the burstable option to OFF (in fact I could by tweaking the theme)

- I have a user who had exceeds his bandwidth limit. His account had been created on february 12th. I told him, I'd wait until his birthday date, to send him an invoice for the exceedent bandwidth used. But on the March 1st, his bandwidth data has been reseted. So I can't know how much he exceeded his bandwidth during his one month subscription (ended on march 11th), also I couldnt invoice this bandwidth's going beyond to him.

Maybe it is not related to the 1.9 release, but it could be great to have :
- an email alert to the box admin when a siteworx account reach his bandwidth limit
- the ability to allow or disallow the burstable option (if the box admin disallow it, the siteworx user couldn't allow it)
- Be sure to be able to follow up the exceed bandwidth during every birthday period (I mean, If a siteworx account is created on xxxx 10th, the bandwidth used should not be reseted before the 9th of the next months) and receive an email alert when the bandwidth used is reseted (only in case of the limit has been reach).

Regards
Pascal

[Justec]

I've shut off my AW and Analog stats. The webserver didn't shut down today (but then again it has'nt happen everyday even with the stats running).

I will leave them off for about a week and see if that resolves the problem. It seems I'm the only one that has had this problem of Apache shutting down and not restarting during the stats program running.

[IWorx-Paul]

Hello ;)

Just a question relating to the 1.9 release :

- Did you upgrade the "create siteworx account" parameters' API to have the language option, spam option, ... ?
The 5th parameter to the account_info variable, if provided, will be the language for the created account.
Examples:
'en-us'
'fr'
Default is en-us.

There's no spam-related stuff in the API yet.


About the bandwidth limit and the burstable option (not sure it is related to the 1.9) :

- when a user exceeds the limit of bandwidth there is no mail alarm sent to the administrator of the box. It's a shame, as I can't check all account every days and I can't force the burstable option to OFF (in fact I could by tweaking the theme)

- I have a user who had exceeds his bandwidth limit. His account had been created on february 12th. I told him, I'd wait until his birthday date, to send him an invoice for the exceedent bandwidth used. But on the March 1st, his bandwidth data has been reseted. So I can't know how much he exceeded his bandwidth during his one month subscription (ended on march 11th), also I couldnt invoice this bandwidth's going beyond to him.

Maybe it is not related to the 1.9 release, but it could be great to have :
- an email alert to the box admin when a siteworx account reach his bandwidth limit
- the ability to allow or disallow the burstable option (if the box admin disallow it, the siteworx user couldn't allow it)
- Be sure to be able to follow up the exceed bandwidth during every birthday period (I mean, If a siteworx account is created on xxxx 10th, the bandwidth used should not be reseted before the 9th of the next months) and receive an email alert when the bandwidth used is reseted (only in case of the limit has been reach).

Regards
Pascal

Neither of these two issues are related to 1.9, but they are very good ideas. I'll move them to the Feature Requests section.

Paul

[pascal]

Thanks Paul,


Neither of these two issues are related to 1.9, but they are very good ideas. I'll move them to the Feature Requests section.


Sorry I should write all these feature requests in the good forum


The 5th parameter to the account_info variable, if provided, will be the language for the created account.
Examples:
'en-us'
'fr'
Default is en-us.


Are you sure it is the 5th parameter ? Here are the parameters I have in the account_info variable.


$ai_pseudo,
$ai_email,
$ai_passwd,
$ai_domaine,
$ai_ip


Is the language option will be after or before the $ai_ip ?

Thanks

Pascal

[Justec]

InterWorx 1.9.1?

What is included in this minor version upgrade? :confused:

By the way with my stats turned off my webserver stayed up for the second straight day.

Thanks,

[timryberg]

InterWorx 1.9.1?

What is included in this minor version upgrade? :confused:

By the way with my stats turned off my webserver stayed up for the second straight day.

Thanks,
assuming it's like 1.8.1 it's just a bug fix since as you can see there was a lot of functionality added to 1.9.0. I see Paul has a post about it in the Anouncements forum.