My Cpanel updates are broken

[ozzi4648]

My Cpanel updates keep updating the same old version. I know the latest version is Release-85 but mine will not update past Release 47. Anyone else having this problem.

==& Checking to see if you have the latest version.....Compare: Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-21.2mdk != Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-20.2mdk
Nope! You have 5.2.0-STABLE_47

 

[FWC]

47 was the last STABLE release until about an hour ago. 85 was an EDGE version. If you run /scripts/upcp now you'll get STABLE-90.

 

[ozzi4648]

[quote:1224f69465][i:1224f69465]Originally posted by FWC[/i:1224f69465]

47 was the last STABLE release until about an hour ago. 85 was an EDGE version. If you run /scripts/upcp now you'll get STABLE-90.[/quote:1224f69465]

My system keeps says this:

==& Checking to see if you have the latest version.....Compare: Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-21.2mdk != Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-20.2mdk
Nope! You have 5.2.0-STABLE_47
==& Fetching the main installation program; please be patient...done.

Its still wrong. It says Nope! You have 5.2.0-STABLE_47 which means it has detected the fact that i am not running the latest stable. Something is wrong! Check it. Further down it says this.

Unable to open logfile /var/log/melange.log - Logging disabled.
--& Administrator Features: Disabled
--& System Messages: Off
--& User Channels: Enabled
--& Anonymous Channel: Enabled
--& Only unique nicknames allowed: No
--& Guest login allowed: Yes
--& Users are allowed to change their nicknames: Yes
--& Default Security Policy: ALLOW ALL HOSTS
--& List of hosts NOT allowed to connect:
--& Default BannTime Setting [sec]: 3600
--& Max Idle Time [sec]: 0
--& LogLevel: 3
--& ServerPort: 6666
--& Message Logfile: disabled
--& Logging Activated: 0

I know why to. A few days ago i switched to the edge release-85. I wanted to test the new phpmyadmin release. Then i didnt want to run the Edge release anymore so i set my update options back to STABLE. On the next update the stupid thing rolled my updates back to STABLE-47. Since then its been stuck at this release without updating.

The code should be checking this.

If update options changed, it should check to see if the stable release has reached the Edge release, if not there should be no updates allowed until the stable release reaches the same release level as the edge release if you decided to switch from one update option to another. That way you dont get rolled back to some old release.

 

[dolphyn]

Or maybe the manual update should give a choice regarding which version to upgrade to, or at least some indication of what version will result from the upgrade, before proceeding.

It's just a thought.

 

[haze]

[quote:79d618d4bb][i:79d618d4bb]Originally posted by ozzi4648[/i:79d618d4bb]

[quote:79d618d4bb][i:79d618d4bb]Originally posted by FWC[/i:79d618d4bb]

47 was the last STABLE release until about an hour ago. 85 was an EDGE version. If you run /scripts/upcp now you'll get STABLE-90.[/quote:79d618d4bb]

My system keeps says this:

==& Checking to see if you have the latest version.....Compare: Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-21.2mdk != Cpanel-5.2.0-STABLE_47-Linux-i686-glibc-2.1.3-20.2mdk
Nope! You have 5.2.0-STABLE_47
==& Fetching the main installation program; please be patient...done.

Its still wrong. It says Nope! You have 5.2.0-STABLE_47 which means it has detected the fact that i am not running the latest stable. Something is wrong! Check it. Further down it says this.

Unable to open logfile /var/log/melange.log - Logging disabled.
--& Administrator Features: Disabled
--& System Messages: Off
--& User Channels: Enabled
--& Anonymous Channel: Enabled
--& Only unique nicknames allowed: No
--& Guest login allowed: Yes
--& Users are allowed to change their nicknames: Yes
--& Default Security Policy: ALLOW ALL HOSTS
--& List of hosts NOT allowed to connect:
--& Default BannTime Setting [sec]: 3600
--& Max Idle Time [sec]: 0
--& LogLevel: 3
--& ServerPort: 6666
--& Message Logfile: disabled
--& Logging Activated: 0

I know why to. A few days ago i switched to the edge release-85. I wanted to test the new phpmyadmin release. Then i didnt want to run the Edge release anymore so i set my update options back to STABLE. On the next update the stupid thing rolled my updates back to STABLE-47. Since then its been stuck at this release without updating.

The code should be checking this.

If update options changed, it should check to see if the stable release has reached the Edge release, if not there should be no updates allowed until the stable release reaches the same release level as the edge release if you decided to switch from one update option to another. That way you dont get rolled back to some old release.

[/quote:79d618d4bb]
The latest stable release still is 47, unless you are running freebsd.

 

[FWC]

[quote:0d305d5fef][i:0d305d5fef]Originally posted by iminteractive[/i:0d305d5fef]

The latest stable release still is 47, unless you are running freebsd.[/quote:0d305d5fef]I need to read more carefully on the Layer 2 page.