Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] System Error! An Error occured! Error ID: xx #134

Closed
2 of 7 tasks
Daeloran opened this issue Nov 20, 2020 · 6 comments
Closed
2 of 7 tasks

[BUG] System Error! An Error occured! Error ID: xx #134

Daeloran opened this issue Nov 20, 2020 · 6 comments
Assignees
Labels
other:not_a_bug All bug reports that originally started as bugs, but ultimatelly turned out to be "something else". other:resolved All resolved issues that do not fall into any other category other All issues that do not have a specific category

Comments

@Daeloran
Copy link

Daeloran commented Nov 20, 2020

Problem description

After a fresh install of the first universe and after a restart of the server or of the Apache service we get the error "

System Error! An Error occured!" on the overview page.

I've checked the error.log of mysql and apache and found an error on apache's logs.

image

I didn't modify files yet.

Engine details

  • Engine version:
    • `version 1.0.0
    • commit COMMIT_HASH (sorry I don't know where to find it)
  • Custom modifications:
    • Yes
    • No
  • Environment:
    • local
    • testing (inaccessible from the outside)
    • production (accessible from the outside world)
  • Configuration:
    • Game speeds: 1
    • Debris settings: 50
    • Any other relevant config entry

Steps to reproduce

Prerequisites:
Do a fresh install on a debian
Mariadb latest
PHP 7.3
Restart the server after create a Universe

image

Desktop:

  • OS: Windows 10
  • Browser: Edge, Opera, Firefox
  • Version: latests

Thank you for your Help

@Daeloran Daeloran added bug All bug reports bug:unconfirmed All new bug reports that are yet to be confirmed (eg. by providing more details) labels Nov 20, 2020
@Daeloran
Copy link
Author

Daeloran commented Nov 20, 2020

I get this error (more precise I think) from the database

Field 'buildQueue' doesn't have a default value
INSERT INTO _planets (id, metal, crystal, deuterium, last_update, metal_perhour, crystal_perhour, deuterium_perhour, energy_used, energy_max) VALUES (1, '588.26147783', '1093.3766222433', '129.94359444333', '1605866375', '175', '48', '13', '-106', '117') ON DUPLICATE KEY UPDATE metal = VALUES(metal), crystal = VALUES(crystal), deuterium = VALUES(deuterium), last_update = VALUES(last_update), metal_perhour = VALUES(metal_perhour), crystal_perhour = VALUES(crystal_perhour), deuterium_perhour = VALUES(deuterium_perhour), energy_used = VALUES(energy_used), energy_max = VALUES(energy_max)
File: /overview.php
User: Lupink[1]

@mdziekon
Copy link
Owner

Hi @Daeloran,

quickly looking at the attached SQL error, it seems that you did not disable STRICT_TRANS_TABLES as mentioned in the installation guide (https://github.com/mdziekon/UniEngine#installation), as this looks very similar to another report (#118).

Could you please verify that option on your instance's database?

@Daeloran
Copy link
Author

HEllo @mdziekon

Thank you for your fast answer.
I disable the STRICT_TRANS_TABLES with the command mysql -u root -p -e "SET GLOBAL sql_mode = 'NO_ENGINE_SUBSTITUTION';". I have too because my Universe don't create if I don't do it (get an sql error at the installation).

I have re-create my site/DB for now.

@mdziekon
Copy link
Owner

To clarify, are you saying that disabling STRICT_TRANS_TABLES and recreating the DB did, or did not solve the problem?

@Daeloran
Copy link
Author

Excuse me,

Recreating my DB solve the problem.

Thank You

@mdziekon mdziekon added other All issues that do not have a specific category other:not_a_bug All bug reports that originally started as bugs, but ultimatelly turned out to be "something else". other:resolved All resolved issues that do not fall into any other category and removed bug All bug reports bug:unconfirmed All new bug reports that are yet to be confirmed (eg. by providing more details) labels Nov 20, 2020
@mdziekon
Copy link
Owner

Sure thing, I'll close the issue now and mark it as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other:not_a_bug All bug reports that originally started as bugs, but ultimatelly turned out to be "something else". other:resolved All resolved issues that do not fall into any other category other All issues that do not have a specific category
Projects
None yet
Development

No branches or pull requests

2 participants