I'm experiencing an issue using Sophos Labs Intelix Dynamic file analysis: https://api.labs.sophos.com/doc/analysis/file/dynamic.html
For some files submitted, the API returns 202 for several minutes, then returns 404, as if the job is suddenly lost. There is no explanation or report provided. I did not experience this issue until this morning when suddenly it happened for 7 different files, although we have not made any code changes.
Why is this happening and what are we supposed to do to handle it?
Some example dynamic analysis jobIDs which now return 404: 10c37c488e86b6871c3f6224ff5273e1, bc900e7bfb8bb25e1f8f127dc25ab8fe, 48cda26c2e3cb54d0b3f4b79ac1ddb7e
Also, is this the correct forum for support requests? I am also trying to go through https://support.sophos.com/support/s/sophos-technical-support but they don't seem to have any knowledge or understanding about Intelix API. My credentials for the API don't appear to be linked to any kind of support portal?
Thanks!
I'm investigating by days with no results about this exception that my NextJS app is currently throwing, in particular when I try to open a single specific URL:
502: BAD_GATEWAY
Code: NO_STATUS_CODE_FROM_FUNCTION
ID: zrh1:4zx5l-1572269318137-64d401b5d058
Here's the screenshot:
Basically, I have on https://lucacattide.dev/about/en a page that this app should open. This is linked to a MongoDB third-party cloud API platform - Squidex - which is responsible to populate the page itself, via GraphQL queries. The app uses Apollo as GraphQL client. The app instead, is hosted on ZEIT.co serverless cloud, with Now 2.0 version.
During the development process, everything works fine. The page loads up and data is fetched in the right way. Notice that for development, I'm working on now-dev environment instead of a custom Express server, in order to reproduce the production one, as suggested by ZEIT itself.
The exception is being thrown on the production environment - the live one on the hosting platform, not on localhost; the main problem is that no errors are being shown on live logs or local development. So I'm literally going mad in inspecting the possible cause.
I've already tried to test the involved page, by splitting it in sections and trying to exclude child components, or focusing the inspection on the GraphQL query. But the first hasn't produced results and the latter works fine in every environment.
As last try, I deleted and re-created the back-end contents related to that page, because in the past I had a similar issue due to an old GraphQL edited schema that didn't reflected its modifications through the API - so in that case I was still receiving 502 errors. But this time it didn't worked.
Anyone could help me to understand what's going on, please?
Thanks everyone in advance
The issue was caused by an incompatibility between the d3-cloud library and the Now environment.
By replacing it with the react-wordcloud one, the error has been solved.
Thanks everyone for your assistance.
I am using the IBM Cloud Object Storage with Swift API on IBM Bluemix as seen here https://console.bluemix.net/catalog/infrastructure/object-storage-group.
I need to get the newest version of an object, or to know if it was deleted. To do so I use the X-Newest header flag in the request, but still I can get an object that was already deleted. Is there a known problem with this flag? Is it supported by the storage service? If it is, can you help to investigate why it happens?
Problematic scenario (Swift local client):
add an object
delete this object
pull this object (Get or Head) with X-Newest flag
and expect always to get "Object Not found" 404 status code (because it was deleted in the previous step). But in reality, sometimes I get this object back although it was deleted. Swift is eventually consistent, and without this flag, it would be a normal behavior. But with this flag, I should not get old versions of the object.
Do you know why it happens?
We are using Node.js module nano to interact with Cloudant instance on Bluemix. Suddenly today we have started getting the below errors while getting data from a view in a Cloudant instance. Any clue what might be wrong?
[{couch_os_process,prompt,3,[{file,"src/couch_os_process.erl"},{line,65}]},
{couch_query_servers,'-map_docs/2-fun-1-',2,
[{file,"src/couch_query_servers.erl"},{line,243}]},
{lists,map,2,[{file,"lists.erl"},{line,1237}]},
{couch_query_servers,map_docs,2,
[{file,"src/couch_query_servers.erl"},{line,239}]},
{couch_view_updater,view_compute,2,
[{file,"src/couch_view_updater.erl"},{line,256}]},
{couch_view_updater,do_map,2,
[{file,"src/couch_view_updater.erl"},{line,161}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1261}]},
{couch_view_updater,do_maps,4,
[{file,"src/couch_view_updater.erl"},{line,153}]}]}
It appears that the indexer is crashing trying to index a particular document. Probably you made a change to your documents, likely the ingestion of a larger document. One indication that it is a 'recent' change to a document causing the crash is to query the view with stale=ok. This will request a response from the last built version of the index (with the last correct version of the document). If this returns correctly it means that the issue is caused by a recent change attempting to be indexed.
This may be an intermittent issue due to a login and application management issue in the US-South region. You can track Platform and Service issues at the Bluemix Status page. If the system status is okay and you still get these errors, open a Bluemix Support ticket.
It's probably a problem with one of the Map Reduce views you have defined on the design document that contains the view you are accessing.
I am not able to create an SSO service. Earlier I was seeing errors similar to those mentioned in this post. Now it seems to be creating the service, but where I usually see the selections to use SAML, Facebook, etc, I just see a blank, white space.
I don't see anything in the status page indicating that there is a known problem.
I am aware of a temporary problem for SSO service yesterday morning (UTC) also reported in the status page. Today the service seems to be up and running and no issues have been reported yet. From the time you asked the question in this forum, I think you might have seen some tailing problems while the service was coming back alive.
If you still should see this behavior today I suggest you to inform Bluemix Support as described in the post you linked in your question.