I can't access my profile. The He's Dead Jim code is: a62c5e87457b371e

Edit: Comments on my posts isn't working for me either, the code is: 4b6443b84fa7e6a1

broken post #818296

TonyLemur said:
Tonight's upgrade is done, and since it was a particularly complex upgrade, there's a decent chance that some things are broken that we haven't found yet. If you receive any errors or see something that seems like it's not behaving correctly, please report it here!

found some broken submissions :
Give this to an admin to report the issue: 4c0f8711900d3ebd
Give this to an admin to report the issue: 10fec8406c3bd4ee
Give this to an admin to report the issue: 1507a75fabc54252

cheers

I'm beginning to think it's not just broken posts. When I accessed the site from mobile the entire /pokemon tag results in a Error Code 500.

DragonFox69 said:
I can't access my profile. The He's Dead Jim code is: a62c5e87457b371e

Edit: Comments on my posts isn't working for me either, the code is: 4b6443b84fa7e6a1

I can access mine, but comments on my submissions get an error (e2ec394143c2b57e).

welp

I tried searching for my posts and got another error (440a090c46e97037)

When I go in to a post,something come out

He's dead, Jim
Something went horribly wrong...
Give this to an admin to report the issue: 1e35c62437dd0bfe

What is this?

The Tag History link at the top of the Posts section is broken too. Code: c484344db86ee2b6

Edit: So is the Random link. Code: 6366a005819a7ad4

I continually get errors on a specific post. And they're different each time I refresh. Here's 3 of them.

He's dead, Jim

Something went horribly wrong...

Give this to an admin to report the issue: 040d454eedf23a6f

He's dead, Jim

Something went horribly wrong...

Give this to an admin to report the issue: 871063e3e28fd7ad

He's dead, Jim

Something went horribly wrong...

Give this to an admin to report the issue: b56a36948ca83d98

With a bit more testing it seems to be the Pokemon tag doing it.

I don't think it's just the /pokemon tag. The entire /nintendo tag yields an error: 1427eb36a9ef9e24

well so far I haven't been able to see any working images with Pokemon in it

however I have seen working images with Nintendo characters with the proper tags

you can't search for Nintendo you get an error but if you find any Nintendo images, minus Pokemon, you will see them fine. This is not true for any Pokemon images, they just won't work

Aside from Jim's rotten clone corpses showing up all over the place, the message about the pictures showing the actual source image is wrong. post #814864 still isn't showing right.

CaesarSalad said:
every single post tagged /pokemon gets me a 500 error

error code was 362ae3629c8d0c3d

i tried multiple posts and the tag itself, nothing seems to work and it only seems to be broken for /pokemon

Same for me

Trying to access my profile page consistently gives me a 500 error. Interestingly though, it appears to be because of my avatar. Having post #552242 causes an error, but having post #771658 didn't. Also, if I try to view the page while not logged on, I can still view it (I'm guessing because avatars aren't displayed on profile pages unless you're logged on). Strangely, the pictures I can't view and the profile pages I can't view don't match up perfectly. For example, I can't view this picture post #773018, but I can view CaesarSalad's profile page.

Code from one of the times I tried to view my profile: db190e5aed0ab382

Dammit Nintendo. Well Hopefully someone finds a legal workaround, if that is indeed the problem.

here is the error code:330b8dacf1fa2c0f

"he's dead jim" error on: https://e621.net/post/show/773393/2015-absurd_res-animal_genitalia-animal_penis-anus

error code: 4c4dc835ebc92375

Images and profile pages are working again for me.

Page 3 of this thread, however, now displays an error: https://e621.net/forum/show/181712?page=3
Code: 5b4410281d0b8f83

EDIT: page 3 is working again.

Got the error 500 (f253e104a2abc827) by searching comments for various strings with ', such as "isn't tagged".

These error codes are interesting. Does the server hash the error message after logging it, and store it in the database under that hash key (the "error code"), so that you can maximize the amount of info you have about what's happening server-side, and exactly when it happened? It's a sensible idea.

savageorange said:
These error codes are interesting. Does the server hash the error message after logging it, and store it in the database under that hash key (the "error code"), so that you can maximize the amount of info you have about what's happening server-side, and exactly when it happened? It's a sensible idea.

It generates a random hexadecimal string and logs it alongside the error so a dev can search for it later.

Genjar said:
Got the error 500 (f253e104a2abc827) by searching comments for various strings with ', such as "isn't tagged".

I rewrote* the comments search from scratch recently to add several new features (order by vote), as well as fix various searching weirdness (such as not being able to search for both a username and text). The issue you mentioned happens to already be fixed in that update.

*coming soon™

The related tags are rather messed up for me, don't know if its a known issue or not. But for example when i put the tags: nintendo nude and open_mouth in i get these as related tags:

And allot of those are just coppies of tags not having to do anything with the original tag its suggest from.
Its a bit difficult to be able to know what the tags are normally linked to and if i am spelling them correctly (use the sugested tags systems almost always for tagging, after having put in what i think is pictured)

parasprite said:
I had no idea those were enabled in blips. TIL

Can you give me an example of a pool to look at?

If you are doing it through the mode menu, change from "add to favorites" to "remove from favorites". I hope to merge those at some point but my javascript-fu is lacking. :x

If you are doing it through the post page:

• Is it every post or just certain posts? If you aren't sure, try favoriting a post then unfavoriting it.
• Can you give an example post?
• What browser/OS are you using?
• Are you using a proxy of some sort? (including things like Tor)

The unfavorite button will be there the first time i favorite it but if i refresh the page it's only the favorite button there, and when i click it, it just tells me i already favorited it, the unfave button doesn't show up again if i faved it one time

I'm not able to submit new pictures

Upload from FA gives out
Error: Source couldn't be opened: Permission denied - /home/e621/e621-production/releases/20160126060000/public/data/832dda22cb5dbc14304434e9e3813318.upload

Direct upload gives me just a "He's dead, Jim"

"I don't want to be a bag of dicks", but it seems that uploading has attracted issues again.
I try posting from a DA direct source, and get:
Error: Source couldn't be opened: Permission denied - /home/e621/e621-production/releases/20160126060000/public/data/f31bb63917c6cffe6499ea72e397bb75.upload
Uploading the same image via file got a 500 error.

mabit said:
I'm not able to submit new pictures

Upload from FA gives out
Error: Source couldn't be opened: Permission denied - /home/e621/e621-production/releases/20160126060000/public/data/832dda22cb5dbc14304434e9e3813318.upload

Direct upload gives me just a "He's dead, Jim"

EmoCat said:
"I don't want to be a bag of dicks", but it seems that uploading has attracted issues again.
I try posting from a DA direct source, and get:
Error: Source couldn't be opened: Permission denied - /home/e621/e621-production/releases/20160126060000/public/data/f31bb63917c6cffe6499ea72e397bb75.upload
Uploading the same image via file got a 500 error.

Sorry about that. During the latest deploy, I messed up the directory structure a bit. Uploads should work as intended now.

parasprite said:
What were you doing to get that?

I was trying to see an image. The interesting part was that I could still see the rest of the posts but not that specific one. Can't remember which one it was.

NotAPervert said:
I was trying to see an image. The interesting part was that I could still see the rest of the posts but not that specific one. Can't remember which one it was.

Gotcha. We had some issues with certain posts due to an obscure bug that only applied to a handful of images. The posts should have all been fixed individually but if you come across it again let us know.

Just tried to upload a pic, spouted out a "He's Dead, Jim" error. Ugh.

post #796364

When I click on the ? next to the artist tag:

He's dead, Jim
Something went horribly wrong...
Give this to an admin to report the issue: cb2e35a7334610746050144b83e399ef

fox_whisper85 said:
Just tried to upload a pic, spouted out a "He's Dead, Jim" error. Ugh.

I think it's just a simple issue with one of the apps (so trying a couple times will likely work), so I've let Spight know. Try to re-upload it again; if you get another error, I'd appreciate it if you could link the error code so we can look it up.

Munkelzahn said:
post #796364

When I click on the ? next to the artist tag:

He's dead, Jim
Something went horribly wrong...
Give this to an admin to report the issue: cb2e35a7334610746050144b83e399ef

Fix sent. Thanks for letting us know.

parasprite said:
I think it's just a simple issue with one of the apps (so trying a couple times will likely work), so I've let Spight know. Try to re-upload it again; if you get another error, I'd appreciate it if you could link the error code so we can look it up.

Fix sent. Thanks for letting us know.

Yeah, it only happened once, so I can't reproduce it, at least for now but if does happen again, I'll let you know...sorry.

parasprite said:
I think it's just a simple issue with one of the apps (so trying a couple times will likely work), so I've let Spight know. Try to re-upload it again; if you get another error, I'd appreciate it if you could link the error code so we can look it up.

Got the same thing, fift time it worked. No error codes at all.

parasprite said:

Munkelzahn said:
post #796364

When I click on the ? next to the artist tag:

He's dead, Jim
Something went horribly wrong...
Give this to an admin to report the issue: cb2e35a7334610746050144b83e399ef

Fix sent. Thanks for letting us know.

Not live yet though, right? Because if that fix was already made live, it may still be a problem. I just got the same error a minute ago. So I'll stick the info for that below in case it turns out to still be acting up somehow. Also noticed an additional symptom which may or may not matter.

furrypickle said:
Not live yet though, right? Because if that fix was already made live, it may still be a problem. I just got the same error a minute ago. So I'll stick the info for that below in case it turns out to still be acting up somehow. Also noticed an additional symptom which may or may not matter.

The normal creating artist wiki link for this artist (generated by clicking the ? in front of the artist's tag on an image): https://e621.net/artist/create?name=yoko-darkpaw
error code from the dead jim page: e92756a4c3c44ccbadf6a02faf646a2f

Note: I did successfully create an artist wiki page for this tag by using a workaround (going directly to the artist wiki section and clicking 'add' and filling it in from scratch.) So now an artist page for this one exists here .

Normally, this would mean that the site would now auto-sense that there's a wiki existing for that name now, and would automatically redirect from that link listed above and take you to the existing artist wiki instead of offering to "create" one anymore, because creating it is done. But clicking that link above still gives the same creation error it gave before any wiki existed. And I don't know if that's significant.

[/quote]

No, it's not live. It'll be sent on next deploy most likely.

You can also delete the "?name=furrypickle from the end of the URL to get to the create page (the name= is what is causing the error).

Not sure if this is related to the January update, but editing blips often results in e621 denying the edited text and remaining the same, especially when reaching the character limit.

HotUnderTheCollar said:
Not sure if this is related to the January update, but editing blips often results in e621 denying the edited text and remaining the same, especially when reaching the character limit.

With the methods we used to use, errors tend to wipe pages. I've been trying to get the newer "non-wiping" method implemented across the site but it's not a 100% drag and drop solution. I'll make a note to start working on that for blips though since I know the 255 char limit would make that particularly annoying to use.

Edit: Oh...I see what you mean now. Yeah that's pretty bad.

What's the status of flash files? I know asking won't make things faster nor do I want to seem like someone complaining about completely free website and service...

One artist just tried modifying their work and reuploading flash two times in addition to other users upload assuming that the file itself was corrupted or incompatible with the site.

post #833210 post #833335 post #833337

Mario69 said:
What's the status of flash files? I know asking won't make things faster nor do I want to seem like someone complaining about completely free website and service...

One artist just tried modifying their work and reuploading flash two times in addition to other users upload assuming that the file itself was corrupted or incompatible with the site.

post #833210 post #833335 post #833337

Mario69 said:
What's the status of flash files? I know asking won't make things faster nor do I want to seem like someone complaining about completely free website and service...

One artist just tried modifying their work and reuploading flash two times in addition to other users upload assuming that the file itself was corrupted or incompatible with the site.

post #833210 post #833335 post #833337

A fix was sent tonight, new uploads should come through fine, we just have to manually fix the ones already uploaded.

HotUnderTheCollar said:
Not sure if this is related to the January update, but editing blips often results in e621 denying the edited text and remaining the same, especially when reaching the character limit.

Semi-confirming this, happens as well when posting a new reply and exact limit is hit (255 / 255 characters)

247/255 seems to work fine: blip #49453

(Should this be here or the general bug section?)

Related:

forum #191298 - Anchor tags do weird things when:*
forum #184896 - Whitespace lines parsed as paragraphs for bullet points

Bug(?):

My account can't be accessed and keeps spouting off with

"He'd dead, Jim"

Error: 14a4b62a688d91305130a4179823e178

fox_whisper85 said:
My account can't be accessed and keeps spouting off with

"He'd dead, Jim"

Error: 14a4b62a688d91305130a4179823e178

It appears to be cycling errors in and out all over the place. It gave me a different error for your profile, then I tried again and accessed it.

Furrin_Gok said:
It appears to be cycling errors in and out all over the place. It gave me a different error for your profile, then I tried again and accessed it.

Right, it keeps changing the errors, what should I do? I had to press F5 eight times to access it, I hope they look into this. I cleared the cache and ran ipconfig /flushdns and still it doesn't help make this go away. Didn't do this yesterday. Are they looking into this? What's causing this? I take it it's pretty bad.

Broken post #701559

And I'm getting "He's Dead Jim" errors for my account -_-

b805648bc5fd964d4eb1120d1cbce825

I keek getting errors.
5 0 0
He's dead, Jim

Something went horribly wrong...

Give this to an admin to report the issue: 426db3cf5b66273e5a4f03c9e563ffcc

Apparently, nobody reported this yet, so... several users were unable to set the correct artist tag for post #848667. When we enter the "gray--day" tag, it always automatically shortens to "gray-day".

On a side note, I got no errors 500 on upload attempts for at least 2 weeks now, so good job at fixing that.