The ultimate support channel for all things MISP. Please come prepared. Bring log files and turn off SELinux. Please contribute your new knowledge to https://github.com/MISP/misp-book/tree/master/faq Error logs: /var/www/MISP/app/tmp/logs/error.log
chrisr3d on main
fix: [python doc] Updated instr… (compare)
cvandeplas on main
Fixes broken GH taxonomy links Merge pull request #282 from 00… (compare)
SteveClement on main
chg: [doc] removed trailing spa… fix: [pdf] PDF conversion works… Merge branch 'MISP:main' into m… and 1 more (compare)
SteveClement on main
chg: [workflow] PDF fails, putt… chg: [workflow] PDF fails, remo… Merge branch 'MISP:main' into m… and 1 more (compare)
SteveClement on main
chg: [workflow] use node_module… chg: [dbg] Workflow chg: [dbg] Workflow, split plug… and 8 more (compare)
SteveClement on main
chg: [doc] Made it working with… new: [workflow] first tentative… chg: [workflow] because npm is … and 4 more (compare)
adulau on main
chg: [honkit] fixes (compare)
adulau on main
chg: [workflow] because npm is … (compare)
adulau on main
chg: [workflow] because npm is … (compare)
Hello, I recently was "given" an extremely outdated version of MISP. After much debugging and updating I finally have a working instance. Now when I try to pull events it gives me the following errors:
2022-08-09 13:27:10 Notice: Undefined index: Attribute in [/var/www/MISP/app/Model/Event.php, line 7546] Warning Error: Invalid argument supplied for foreach() in [/var/www/MISP/app/Model/Event.php, line 7546]
This one is potentially interesting. I can see that being an issue
Hello, I have updated MISP today to " v.2.4.160 " and after reload " Diagnostics " tab I can see a lot of " Benign Deltas " to update data base:
I copy each one and conencted on my DB instance I run all using MISP user and using MISP DB, but after update " Diagnostics " tab nothing update.
su misp
if you want it anyway)
Forllow the error:
[2022-08-11 21:11:14] main.ERROR: {"queue":"prio","id":"d9a6a73fc79e47af2186f933931578f4","class":"AdminShell","args":[["runUpdates",9438]]} failed: SQLSTATE [22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column misp
.jobs
.status
at row 1 {"type":"fail","log":"SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column misp
.jobs
.status
at row 1","job_id":"d9a6a73fc79e47af2186f933931578f4","time":86,"worker": "45c4f460fd6f:3653"} []
[2022-08-11 21:31:39] main.INFO: got {"queue":"prio","id":"f63246d27af85ffccb6e82e632288523","class":"AdminShell","args":[["runUpdates",9439]]} {"type":"got","args":"[object] (Resque_Job: {\"queue\":\"prio\",\"id\":\"f63246d27af85ffccb6e82e632288523\",\"class\":\"AdminShell\",\"args\":[[\"runUpdates\",9439]]})","worker":"45c4f460fd6f:3653"} []
[2022-08-11 21:31:39] main.INFO: Processing ID:f63246d27af85ffccb6e82e632288523 in prio {"type":"process","worker":"45c4f460fd6f:3653","job_id":"f63246d27af85ffccb6e82e632288523"} []
[2022-08-11 21:31:39] main.ERROR: {"queue":"prio","id":"f63246d27af85ffccb6e82e632288523","class":"AdminShell","args":[["runUpdates",9439]]} failed: SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column misp
.jobs
.status
at row 1 {"type":"fail","log":"SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column misp
.jobs
.status
at row 1","job_id":"f63246d27af85ffccb6e82e632288523","time":108,"worker":"45c4f460fd6f:3653"} []
My problem now is related with another instance and getting another type of error:
[2022-08-11 22:42:45] main.ERROR: {"queue":"prio","id":"e395667a6ae5a466316b84e5e2b194e0","class":"AdminShell","args":[["runUpdates",3063]]} failed: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '183885-14235790-35778' for key 'unique_correlation' {"type":"fail","log":"SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '183885-14235790-35778' for key 'unique_correlation'","job_id":"e395667a6ae5a466316b84e5e2b194e0","time":217,"worker":"2ca66f78eb1c:182"} []
[2022-08-11 22:42:45] main.INFO: got {"queue":"prio","id":"de5f77ae2f6064aaba67540d38b226c6","class":"AdminShell","args":[["runUpdates",3064]]} {"type":"got","args":"[object] (Resque_Job: {\"queue\":\"prio\",\"id\":\"de5f77ae2f6064aaba67540d38b226c6\",\"class\":\"AdminShell\",\"args\":[[\"runUpdates\",3064]]})","worker":"2ca66f78eb1c:182"} []
Hi, after updating MISP to latest version ( v2.4.161 (4d9ea1e4e37eddb4d2974d27e3f64c5f7853fa43) ) we did a pull all from a remote server. We can now see events but after opening them we can't see the attributes.
They are searchable in the list/search attributes section but arent in the view of the event itself. I dont know if its of any importance but we also disabled correlations.
We are getting this error message when viewing event:
Attribute warning: This event doesn't have any attributes visible to you. Either the owner of the event decided to have a specific distribution scheme per attribute and wanted to still distribute the event alone either for notification or potential contribution with attributes without such restriction. Or the owner forgot to add the attributes or the appropriate distribution level. If you think there is a mistake or you can contribute attributes based on the event meta-information, feel free to make a proposal.
Can anyone help please?