update process was aborted prematurely while running update #8216

Hi corE,

Thank you for posting the bug.

Nothing in the logs stands out to me. The 8.x-2.16 update has significant schema additions. More data is being logged, with reports to follow in subsequent releases. It could be an issue creating a table or adding another column. It could also be a query timeout. Do you have a lot of visitors data? How long have you used visitors?

Another user with a different issue could run the update 🐛 SQLSTATE[23000]: Column visitors_title cannot be null Fixed . The problem could be a bug in visitors or an environmental issue on your end. I would need to see more to tell. You can DM me if you want me to take a closer look.

8.x-2.16 database schema changes:

• New table: visitors_counter
• Additional columns on visitors table:
  • route
  • config_resolution
  • config_pdf
  • config_flash
  • config_java
  • config_quicktime
  • config_realplayer
  • config_windowsmedia
  • config_silverlight
  • config_cookie

The 8.x-2.17 release will also add more columns to log more data, with additional reports to follow. The 8.x-2.18 release will have minimum or no schema changes.

@bluegeek9

Thank you for looking at that.

The module did eventually take/install after some page refreshes and cache clearing, However, I was spooked not only by the error & abort warning, but by the complete clearing of all the log entries. So this is why I rolled back. If I'm recalling right there was a long hesitation during the update.php.

Is this normal for the database log messages to be completely cleared? I had a lot of entries in there prior.

I've used visitors for a while now, it's a very useful tool for many things. I cant say I've ever had a problem updating, but the last two updates I've had issues. I'm also having major issues with captcha module and I'm wondering if there is something in Drupal core causing issues.

Perhaps I will try uninstalling/reinstalling it. Would you say that might work to avoid any issues?

Thank you

PS...

I just checked my error logs and there was a error/typePHP regarding visitors. I don't know if it is pertinent or helpful - just thought I'd post it:

Error: Class "Drupal\visitors\EventSubscriber\KernelTerminateSubscriber" not found in Drupal\Component\DependencyInjection\Container->createService() (line 259 of ../core/lib/Drupal/Component/DependencyInjection/Container.php)

#0 ../core/lib/Drupal/Component/DependencyInjection/Container.php(177): Drupal\Component\DependencyInjection\Container->createService()
#1 ../core/lib/Drupal/Component/EventDispatcher/ContainerAwareEventDispatcher.php(136): Drupal\Component\DependencyInjection\Container->get()
#2 ../vendor/symfony/http-kernel/HttpKernel.php(103): Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch()
#3 ../vendor/stack/builder/src/Stack/StackedHttpKernel.php(32): Symfony\Component\HttpKernel\HttpKernel->terminate()
#4 ../core/lib/Drupal/Core/DrupalKernel.php(702): Stack\StackedHttpKernel->terminate()
#5 ../index.php(22): Drupal\Core\DrupalKernel->terminate()
#6 {main}

No one else has reported this issue. I think there is something different in your environment.

"Drupal\visitors\EventSubscriber\KernelTerminateSubscriber" was removed. If you are getting this error, it is either cache or something with your enviroment.

Did you use composer to install Visitors?

bluegeek9 → credited devad → .