InterWorx 2.1.2 Released

We’re happy to announce the release of InterWorx-CP version 2.1.2.

This update will be applied automatically within 24 hours if your server has auto-updates enabled (the default). If you choose to perform the update manually, we recommend logging into your server as root, and running the command:

yum update

If you have any problems with this update please open a Support Ticket.

This release basically consists of all the important bug fixes that have been completed on the current branch of development. The bugs fixed in this release include the following.

  • Numerous bug fixes related to clustering and IP management.

  • Prevent non-critical RRD warnings from getting mailed via Cron.

  • Fix import of MySQL user connecting from wildcard (%) locations.

  • Fix Ensim import failure with “0” disk quota in Ensim Backup format.

  • Remove dedicated IPs that are “owned” by resellers from the list of available IPs for the root NodeWorx user.

  • Fix problem with dedicated IP’s sometimes being reported as “unused” when they are in fact used.

  • Fix account creation failure when accented characters are used in name field.

  • Add easy interface to enable secondary SMTP port (587 by default) on the NodeWorx MTA page.

  • Disallow creation of SiteWorx accounts with domains with no TLD.

  • Fix web log rotation to delete the oldest saved logs instead of newest.

  • Remove non-critical warning messages during account import.

  • Fix import of very large Plesk backup files.

  • Allow reseller SiteWorx account editing when SiteWorx account limit is reached.

  • Force domain name to lower case during account creation.

  • Fix NFS start/stop functionality.

  • Fix missing ScriptWorx package option when creating an account via API with ModernBill.

  • Fix random failures during mass transfer/import.

  • Fix bit/byte conversion switch on Bandwidth Graph in SiteWorx.

  • Fix Horde webmail vacation module.

Paul

  • Fix problem with dedicated IP’s sometimes being reported as “unused” when they are in fact used.

I had this problem before and it is the same after the update, is there anything i have to do to correct it or should of it corrected itself with the udpate?

Also, is there any easy way to protect a custom /home/interworx/lib/maildrop/spamfilter file I have created? It gets overwritten everytime there is an update. It’s not a big deal I always keep a backup and I just overwrite the new file, but was just wondering.

Could you open a ticket with your root login information, and we’ll check it out.

Thanks,
Socheat

Thanx Socheat, not sure how that got there, probably something I did over a year ago :rolleyes:

Sweetness

Yay! Now I can let you guys keep coding instead of constantly opening tickets to fix this! :smiley:

No problem. For those who are interested, the problem was that there was a stray “NameVirtualHost” directive at the top of one of his conf files, on an IP that was supposed to be dedicated. We use the NameVirtualHost directive to determine what IPs are shared and what are dedicated, so this was what was throwing off InterWorx.

Just curious… Why the addition of ripMIME?

We used RipMIME for speeding up Plesk imports. Plesk backups are essentially just one huge email with a bunch of MIME-encoded attachments. Our initial/old implementation of the Plesk importer read in the entire file, which was bad for memory/resource usage. RipMIME reads through the file sequentially and dumps out the chunks of encoded data into smaller, more workable files.

Socheat

OK, so not a major deal for most people.

Any word on when FTPS will be coming about? Maybe 2.2? I know the option is there to build it in, but it killed all TCP traffic on my box the last time I did it, so a pre-compiled version would be nice.

Could you please post instructions for successfully enabling the secondary SMTP port (587) and closing down port 25?

I don’t think the inclusion of the alternative port was to replace port 5, merely be in addition to it.

Logon to Nodeworx, and click on the SMTP service name on the front page. On the right hand side of the content page, below the main smtp config, you will what looks effectively like a new service, called alternative smtp port. Click Start to start the service. I found that I had to push it twice to start it, but since then it has worked fine.

Hope this helps.

I don’t think the inclusion of the alternative port was to replace port 5, merely be in addition to it.

Everythingweb is 100% correct. 587 is in addition to and not instead of. port 25 must be open or no mail delivery will happen period regardless of port 587’s status.

Chris

My “Software Updates” section did not list this update. Even after refreshing, it only said “? List updated successfully” and “No software updates are pending.” Both “OS Updates” and “InterWorx Updates” are enabled.

Through SSH, I ran the “yum update” command and it updated to 2.1.2 without any trouble. Is my box incapable of receiving updates via InterWorx?

# yum update
Setting up Update Process
Setting up repositories
interworx-cp-rhe4x        100% |=========================|  951 B    00:00
interworx-cp-noarch       100% |=========================|  951 B    00:00
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for interworx to pack into transaction set.
interworx-2.1.2-17.iworx. 100% |=========================| 674 kB    00:01
---> Package interworx.noarch 0:2.1.2-17.iworx set to be updated
---> Downloading header for interworx-siteworx to pack into transaction set.
interworx-siteworx-2.1.2- 100% |=========================| 131 kB    00:00
---> Package interworx-siteworx.noarch 0:2.1.2-17.iworx set to be updated
---> Downloading header for interworx-nodeworx to pack into transaction set.
interworx-nodeworx-2.1.2- 100% |=========================| 101 kB    00:00
---> Package interworx-nodeworx.noarch 0:2.1.2-17.iworx set to be updated
--> Running transaction check
--> Processing Dependency: ripmime for package: interworx
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for ripmime to pack into transaction set.
ripmime-1.4.0.5-100.rhe4x 100% |=========================| 1.9 kB    00:00
---> Package ripmime.i386 0:1.4.0.5-100.rhe4x.iworx set to be updated
--> Running transaction check

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Updating:
 interworx               noarch     2.1.2-17.iworx   interworx-cp-noarch   50 M
 interworx-nodeworx      noarch     2.1.2-17.iworx   interworx-cp-noarch  2.9 M
 interworx-siteworx      noarch     2.1.2-17.iworx   interworx-cp-noarch  2.1 M
Installing for dependencies:
 ripmime                 i386       1.4.0.5-100.rhe4x.iworx  interworx-cp-rhe4x   47 k

Transaction Summary
=============================================================================
Install      1 Package(s)
Update       3 Package(s)
Remove       0 Package(s)
Total download size: 55 M
Is this ok [y/N]: y
Downloading Packages:
(1/4): interworx-2.1.2-17 100% |=========================|  50 MB    02:01
(2/4): interworx-siteworx 100% |=========================| 2.1 MB    00:04
(3/4): interworx-nodeworx 100% |=========================| 2.9 MB    00:09
(4/4): ripmime-1.4.0.5-10 100% |=========================|  47 kB    00:00
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: ripmime                      ######################### [1/7]
  Updating  : interworx                    ######################### [2/7]
  Updating  : interworx-siteworx           ######################### [3/7]
  Updating  : interworx-nodeworx           ######################### [4/7]
  Cleanup   : interworx                    ######################### [5/7]
  Cleanup   : interworx-siteworx           ######################### [6/7]
  Cleanup   : interworx-nodeworx           ######################### [7/7]

Dependency Installed: ripmime.i386 0:1.4.0.5-100.rhe4x.iworx
Updated: interworx.noarch 0:2.1.2-17.iworx interworx-nodeworx.noarch 0:2.1.2-17.iworx interworx-siteworx.noarch 0:2.1.2-17.iworx
Complete!

The same happened with my box. Could it be 'cause we’re on a 64 bit CentOS?

My 64-bit CentOS box updated just fine.

It’s been my experiencew that the NodeWorx software updates page does not list updates done from the command line, so this is normal.

Are you concerned because the update didn’t happen automatically for you?

Updates are generally anounced here minutes after the RPM’s are uploaded to the updates server. It can take up to 24 hrs for boxes to update atomatically (depending on when your daily cron is set to run).

Unlesss you waited more than 24hrs from when Paul posted the anouncement, I wouldn’t worry about it.