vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   which tasks in daily cleanup and can I disable crob jobs? (https://vborg.vbsupport.ru/showthread.php?t=319182)

helenblog 06-25-2015 01:50 PM

Quote:

Originally Posted by TheLastSuperman (Post 2548574)
you can check the "session" table in the database via phpmyadmin to monitor the number of visitors

I checked session table in phpmyadmin it has over 1000 rows now

I have some questions

how many hours can I set with session timeout?

Are there any ways to modify or changes (in php.ini or vb codes) to make it work properly even in 12 hours or 24 hours?

what is the maximum time i can set for session timeout?

How did cron job work for session timeout and how it will be deleted from session table?

Why it make my server high load when setting session timeout tooooooo high? ( I think it consumed more CPU or RAM to delete these session rows in table, right? thus it makes my Apache (httpd) restart automatically? )


Thanks in advance.

TheLastSuperman 06-25-2015 05:49 PM

^ Some things I do believe I've confused you on... the php.ini and other things I mentioned above were "possible" issues, I didn't know at the time you meant "session timeout" specific setting until later.

I believe from what you've told me here and via pm that I now know, you changed your Session Timeout setting to 12hours instead of 15/30mins.

So with all that being said, lets do a quick test ok?
- Change Session timeout setting to 1800 which equals 30mins a member can stay logged in.
-- Now wait and see if the server restarts (whenever it did daily etc).

*IF the issues subsides after this i.e. the server stops restarting and the odd behavior stops then you know it was in fact your (overly)high session timeout.
**IF the server continues to restart and have issues AFTER being changed to 1800 then we know it was NOT the session timeout being too high.

^ Let us know. After we know 100% that the issue was "Session Timeout" setting, then we can go from there and make changes so members can stay logged in for 12hours without issues BUT not until current problem is fixed ;).


All times are GMT. The time now is 03:06 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01081 seconds
  • Memory Usage 1,715KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (1)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (2)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete