Advertisement:

Author Topic: [Solved] Mysterious problems post-installation  (Read 16230 times)

Offline Naypam

  • Newbie
  • *
  • Posts: 5
[Solved] Mysterious problems post-installation
« on: August 03, 2014, 03:10:10 PM »
So I downloaded the .tar.gz package from the main page and extracted it to a folder, set up nginx with php-fpm and followed the install instructions.

All very good, I ran into two problems during install. The first was that the port specification is a tad ludicrous if PostgreSQL runs on a non-standard port, you have to enter "hostname port=####" instead of what you would expect (used for MySQL for example which is "localhost:####".

Anyway once I figured that out the installation went fine but it threw up some seemingly non-critical errors about some inserts failing. It looked like it had failed to properly parse the SQL statement, breaking on the quotation symbol (I think it wasn't escaping the apostrophe in "Father\'s day"). It didn't seem overly critical to the functioning of the website anyway.

But once things got rolling, logged in, admin account created, I've run across some interesting bugs. I'm going to guess that they're either session/cookie related, cache related or due to the previous errors or PostgreSQL support.

What I've noticed is:

* If you attempt to edit a user account you get a session timed out error, that is if you attempt to change a user's group the session times out. Or if you attempt to edit the user at all.
* Deleting the standard "welcome" topic worked fine, but posts cannot be made. On HTTP POST you are redirected to the same submission form only completely reset (all fields empty).
* Sometimes if you edit options in the administration area nothing appears to change, but it actually *does* change, it's just not reflected in the form data.
* There seems to be hxxp://i.imgur.com/Tl2hNod.png some missing content from the admin menu? (I asked in #smf on Freenode).

I can attempt a second installation to give you more detailed output, but I would like to access an error log to see what's going on. Nothing other than the session timeout is throwing an error.
« Last Edit: August 03, 2014, 07:49:49 PM by Naypam »

Offline Naypam

  • Newbie
  • *
  • Posts: 5
Re: Mysterious problems post-installation
« Reply #1 on: August 03, 2014, 03:41:06 PM »
Code: [Select]
Your settings have now been saved and the database has been populated with all the data required to get your forum up and running. Summary of population:

    Created 63 tables.
    Inserted 912 rows.

Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of your database software.

Technical information about the queries:

    Line #736: ERROR: syntax error at or near "s"
    LINE 4: ...r_holidays (title, event_date) VALUES ('New Year\'s', '0004-...
    ^
    Line #738: ERROR: syntax error at or near "s"
    LINE 2: ..._holidays (title, event_date) VALUES ('Valentine\'s Day', '0...
    ^
    Line #739: ERROR: syntax error at or near "s"
    LINE 2: ...olidays (title, event_date) VALUES ('St. Patrick\'s Day', '0...
    ^
    Line #744: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #745: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #746: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #747: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #748: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #749: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #750: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #751: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #752: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #753: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #754: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Mother\'s Day', '2...
    ^
    Line #755: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #756: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #757: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #758: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #759: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #760: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #761: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #762: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #763: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #764: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #765: ERROR: syntax error at or near "s"
    LINE 2: ...dar_holidays (title, event_date) VALUES ('Father\'s Day', '2...
    ^
    Line #2302: ERROR: syntax error at or near "("
    LINE 2: ...e, description, smiley_order, hidden) VALUES (':\'(', 'cry.g...
    ^

I've run an install a second time on a new database to collect the errors during the population stage.

Offline tinoest

  • Development Contributor
  • Jr. Member
  • *
  • Posts: 183
Re: Mysterious problems post-installation
« Reply #2 on: August 03, 2014, 04:18:02 PM »
You need to change the escape character \ to a ' 

So the line looks like the following:
LINE 4: ...r_holidays (title, event_date) VALUES ('New Year''s', '0004-...

Instead of \ :
LINE 4: ...r_holidays (title, event_date) VALUES ('New Year\'s', '0004-...



Offline tinoest

  • Development Contributor
  • Jr. Member
  • *
  • Posts: 183
Re: Mysterious problems post-installation
« Reply #3 on: August 03, 2014, 04:20:22 PM »
What version of PostgreSQL are you utilising and also what PHP Version

Offline Naypam

  • Newbie
  • *
  • Posts: 5
Re: Mysterious problems post-installation
« Reply #4 on: August 03, 2014, 04:27:47 PM »
What version of PostgreSQL are you utilising and also what PHP Version

I changed the SQL file to make it import fine, so that's all good. Didn't fix any of the other issues though.

PHP 5.5.14 and PostgreSQL 9.3.4-2.

Offline Naypam

  • Newbie
  • *
  • Posts: 5
Re: Mysterious problems post-installation
« Reply #5 on: August 03, 2014, 07:10:18 PM »
Just an update, I installed again (same everything, just a different database name) and it still has the same problems minus the error log being visible (see screenshot above) in the main admin menu.

I can't install on MySQL as it attempts to connect with a different username from the one that I specify?

I type "user1" in the username field for MySQL and the error is 'user2'@'localhost' couldn't connect la de da.

Offline Naypam

  • Newbie
  • *
  • Posts: 5
Re: Mysterious problems post-installation
« Reply #6 on: August 03, 2014, 07:49:25 PM »
Problem solved!

Issue was in the php config file (php.ini, for me /etc/php/php.ini) where I had the post_max_size set to 1k (the default is 8M).

I set it to 256k and everything's running wonderfully. The POST data must have exceeded 1024 bytes in size I should imagine.

Thank you all for your help!