Make WordPress Core

Opened 11 years ago

Closed 11 years ago

#25164 closed defect (bug) (worksforme)

Upgrade 3.5. -> 3.6

Reported by: adamtrlica's profile adamtrlica Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.6
Component: Upgrade/Install Keywords: reporter-feedback
Focuses: Cc:


we have a problem on our webhosting servers with automatic upgrade. When we start update with FTP user, automatic upgrade ends on "Installing latest the version" but it doesn´t write any error. When I delete .maintenance file on FTP it seems OK. After that I can upgrade database and in wp admin I see version 3.6.
On FTP server remain temoporary upgrade files.
When we set apache as a owner of all files and start upgrade under apache user the upgrade ends on "Upgrading database".

FTP server has two users, apache and ftp.
Manual upgrade is OK.

Can you help us?

Thank you

Change History (9)

#1 @jeremyfelt
11 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Severity changed from major to normal
  • Status changed from new to closed

At the surface, this sounds like a permissions issue on the web host. Please try the support forums for troubleshooting: ​

If it turns out to be a bug in core, feel free to reopen this ticket.

#2 @adamtrlica
11 years ago

We have two server users. Apache and FTP user. When we are trying upgrade with FTP user (owner), we use FTP layer for upgrade, it ends on "Installing latest the version".
After that, we tried change owner of all files on server to Apache. The uprage stars without FTP login and ends "Upgrading database". Folders has chmod 755 and files 644, so Apache can write to all files. Where in file permissions is problem please?

Version 1, edited 11 years ago by adamtrlica (previous) (next) (diff)

#3 @adamtrlica
11 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#4 @dd32
11 years ago

  • Milestone set to Awaiting Review

This doesn't sound like a Permissions issue to me, nor does it sound like a regression or a 3.5/3.6-specific thing.

This sounds like a timeout somewhere, I'd enable WP_DEBUG and/or check the PHP error logs (both for PHP, and the Apache logs) looking for a timeout or something.

#5 @adamtrlica
11 years ago

Thank you for answer. WP debug is enabled, but log on the server is empty and debug.log too. Do you have another idea please?

#6 @dd32
11 years ago

Can you try adding this to a mu-plugin, or your themes functions.php file?

add_filter( 'upgrader_pre_install', '_increase_timeout');
function _increase_timeout( $filter ) {
  return $filter;

See if that causes any PHP notices/warnings/logs, or if an upgrade completes.
I'm still fairly certain it's a timeout issue, the WordPress upgrader attempts to set a 300 second (5 minute) timeout, some server configurations won't allow for that to be changed though, and could cause it to time out much sooner than that, causing the symptoms you describe.

#7 @adamtrlica
11 years ago

I am server administrator and I set max_execution_time to 999 sec and it is not help me. It seems that the upgrade will end after display "Installing latest the version" and that is when it stops working. If you want, we can create an access to server for you.

#8 @dd32
11 years ago

If you want, we can create an access to server for you.

You can contact me off trac at dion a to discuss that.

#9 @dd32
11 years ago

  • Keywords reporter-feedback added
  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from reopened to closed

Closing as worksforme pending reporter feedback that points to a bug. Highly unlikely to be a 3.6 regression

Note: See TracTickets for help on using tickets.