Codeigniter 3与RDS随机登出：能否通过框架设置解决？

Hey there, let’s tackle this random logout issue you’re facing with CodeIgniter 3 on your AWS stack. I’ve debugged similar problems before, so here’s a step-by-step breakdown of what to check and fix:

First, head to application/config/config.php and verify these critical session settings:

• Session Driver: If you’re using the default file driver, switch to database immediately. EC2 instances (especially if you’re scaling with multiple servers) don’t share local file systems, so sessions stored on one instance won’t be visible to others. Set:

  $config['sess_driver'] = 'database';
  $config['sess_save_path'] = 'ci_sessions'; // Name of your session table
  

  Make sure your ci_sessions table exists in RDS with the correct structure (CI 3 requires this schema):

  CREATE TABLE IF NOT EXISTS `ci_sessions` (
          `id` varchar(128) NOT NULL,
          `ip_address` varchar(45) NOT NULL,
          `timestamp` int(10) unsigned DEFAULT 0 NOT NULL,
          `data` blob NOT NULL,
          KEY `ci_sessions_timestamp` (`timestamp`)
  );
  

• Expiration Settings: Double-check $config['sess_expiration'] – it’s set to seconds, so 300 would be 5 minutes (which matches your issue). If you want longer sessions, bump this to something like 7200 (2 hours). Also ensure $config['sess_expire_on_close'] = FALSE unless you intentionally want sessions to end when the browser closes.
• Cookie Security: If your site uses HTTPS, set:

  $config['cookie_secure'] = TRUE;
  $config['cookie_domain'] = 'yourdomain.com'; // Match your actual domain
  $config['cookie_path'] = '/';
  $config['cookie_httponly'] = TRUE;
  

  This prevents cookie tampering and ensures sessions are only sent over secure connections.

AWS has a few quirks that can break sessions:

• Load Balancer Sticky Sessions: If you’re using an ELB with multiple EC2 instances, enable sticky sessions (also called "session affinity") temporarily to test – this forces requests from the same user to hit the same instance. Note: This is a band-aid; using the database session driver is the permanent fix.
• RDS Connection Timeouts: Check RDS’s wait_timeout and interactive_timeout parameters (via the AWS RDS console’s parameter group). These default to 8 hours, but if your PHP mysql.connect_timeout or CI’s database timeout setting is too short, it can drop connections mid-session. Add this to your CI database config (application/config/database.php):

  $db['default']['timeout'] = 3600; // 1 hour, adjust as needed
  

  Also monitor RDS CPU/memory usage – if the database is under heavy load, session writes might fail silently.
• EC2 File Permissions: If you stick with the file driver (not recommended), ensure the sess_save_path directory is writable by your web server user (e.g., apache or nginx). Set permissions to 700 and make the directory owned by the web server user.

SSH into your EC2 instance and check these PHP settings (via phpinfo() or editing php.ini):

• Session Garbage Collection: Ensure session.gc_maxlifetime matches your CI sess_expiration value. For example, if CI is set to 7200, PHP should also have:

  session.gc_maxlifetime = 7200
  

  You can override this in CI’s index.php if you can’t edit php.ini:

  ini_set('session.gc_maxlifetime', 7200);
  

• OpCache: If you’re using OpCache, make sure it’s not caching CI’s session files. Verify these settings:

  opcache.enable_cli = 0
  opcache.validate_timestamps = 1
  

  Stale cached session code can cause unexpected logout behavior.

• Enable CI Logs: Set $config['log_threshold'] = 2 in config.php and check application/logs for errors related to session writes, database connections, or invalid session IDs.
• Inspect the Session Table: Run a query on RDS to check if sessions are being saved and updated:

  SELECT * FROM ci_sessions WHERE ip_address = 'your_ip_address';
  

  If sessions disappear or the timestamp isn’t updating, that means CI isn’t saving sessions correctly.
• Test with a Single Instance: If you’re running multiple EC2 instances, shut all but one down temporarily. If the logout stops, you know the issue is related to session sharing across instances.

Most of the time, switching to the database session driver fixes this problem on AWS – file-based sessions just don’t play nice with distributed environments.

内容的提问来源于stack exchange，提问作者Forbs