OSPOS goes back to login page when sales items reaches ~120-140

[mgmamac]

Background information

IMPORTANT: If you choose to ignore this issue report template, your issue will be closed as we cannot help without the requested information.

Please make sure you tick (add an x between the square brackets with no spaces) the following check boxes:

• [x] Reporting an issue of an unmodified OSPOS installation
• [x] Checked open and closed issues and no similar issue was already reported (please make sure you searched!)
• [x] Read README, WHATS_NEW, INSTALL.md and UPGRADE
• [x] Read the FAQ for any known install and/or upgrade gotchas (in specific PHP extensions installed)
• [x] Read the wiki
• [] Executed any database upgrade scripts if an upgrade pre 3.0.0 (e.g. database/2.4_to_3.0.sql)
• [x] Aware the installation code is in bintray (see README), and GitHub master is for developers only and therefore not complete nor stable

Installation information

• OSPOS version is: 3.3.2(release)
• OSPOS git commit hash is: bb309c2 (Is this it? I'm not sure.)
• PHP version is: 7.3.21
• MySQL or MariaDB version is: 5.7.31
• OS and version is: Windows 10 64bit
• WebServer is: Wampserver 3.2.3 64bit
• Selected language is: 1909
• (If applicable) Docker installation:
• (If applicable) Installation package for the LAMP/LEMP stack is:

Issue / Bug / Question / New Feature

Hello! I'm not really knowledgeable in web and database stuff. I was able to make OSPOS work by following instructions from your documentation and youtube videos. I'm hoping that I can help a little by reporting the issue I encountered.

When inputting items on sales tab, once the number of items reaches somewhere ~120-140, the search bar won't show any product whatever you type in. When that happens, if you click any button on the webpage, it will take you back to login page. It happened without fail on 3 consecutive retries even after reboot. If I relogin, all my progress on inputting items on sales tab is gone. I was able to "bypass" the issue by breaking down the sale into 2 or 3 batch of receipts.

I'm using Firefox 92.0.2 64bit.

Thank you!

[jekkos]

@mgmamac kind of hard to help based on this information.. you'll need to post some kinf of error log first. Maybe check your chrome network console to see if there are any status 500 responses and then post the response body here.

[ozzylamberth]

I have entered a total of 350 articles in the sales module in both versions 3.2 and 3.3 and it works without problem except a little slow in the CRUD

Eh ingresado un total de 350 articulos en modulo de venta tanto en la version 3.2 como en la 3.3 y funciona sin problema salvo un poco de lentitud en el CRUD

[jekkos]

I don't think there is anything we can do here unless you provide more information.

[WebShells]

Issue confirmed

OSPOS Installation Info: 3.3.2 - c786d4 Language Code: en-US

Extensions & Modules: » GD: Enabled ✓ » BC Math: Enabled ✓ » INTL: Enabled ✓ » OpenSSL: Enabled ✓ » MBString: Enabled ✓ » Curl: Enabled ✓

User Configuration: .Browser: Chrome .Server Software: Apache/2.4.6 .PHP Version: 5.6 .DB Version: 5.5.5-10.3.27-MariaDB .OS: Linux

File Permissions: » [application/logs:] - 0750 | Writable ✓ | Security Check Passed ✓ » [public/uploads:] - 0750 | Writable ✓ | Security Check Passed ✓ » [public/uploads/item_pics:] - 0750 | Writable ✓ | Security Check Passed ✓ » [import_customers.csv:] - 0644 | Readable ✓ | Security Check Passed ✓

All file permissions are set correctly! Security Vulnerability Warning No security/vulnerability risks.

After listing all items in receiving section once the items reach upto 100+ it's redirecting to login page again. Will check error logs upon next trial and show the result.

[WebShells]

ERROR --> Severity: Warning --> session_start(): Failed to decode session object. Session has been destroyed /maindir/vendor/codeigniter/framework/system/libraries/Session/Session.php 143

[WebShells]

I think it's related to session regeneration destroy ?

[jekkos]

@WebShells were you able to reproduce this issue on your install then?

[jekkos]

Bump @WebShells ?

[WebShells]

@jekkos this happened after reaching a limit of 100 items in receivings ( 3 to 5 mins )

[jekkos]

@WebShells You are probably bumping into the 64 Kb limit of the blob session data column. It's already quite a lot and way more than the initial 4kb cookie limit. We could increase the column size to MEDIUMBLOB (16MB) which should be enough for most usecases. But this might come with a performance hit.

[jekkos]

@ozzylamberth can you try the migration in my pull request, to see if this works and if performance is acceptable?

[objecttothis]

@jekkos is a longblob overkill here? I think a mediumblob would be more efficient, but don't know for sure.

[jekkos]

I think it's mediumblob now (I might still have this message in the commit history, but I fixed the type afterwards).

[jekkos]

Closing this one for now. @ozzylamberth let me know if any issue otherwise.