New instance: Failed to create session ID?
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6.5k
- Forks
- 1.6k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 27
Description
I just installed a new MISP instance, I dumped & reimported the DB from a previous MISP.
I can't login due to the following error:
2017-04-28 16:41:59 Warning: Warning (2): session_write_close() [function.session-write-close]: Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp) in [Unknown, line 0]
I replaced the default /var/lib/php/sessions with /tmp... same issue!?
Work environment
| Questions | Answers |
|---|---|
| Type of issue | Bug? |
| OS version (server) | Ubuntu, |
| OS version (client) | 16.05 |
| PHP version | 7.0 |
| MISP version / git hash | 2.4.72 |
| Browser | All |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the PHP session.save_path configuration and permissions reported in the issue, then reproduce the login failure on the stated Ubuntu/PHP 7.0 environment. Done means MISP can write session data and a user can log in after the database import; no source file or test is identified in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100