Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refinery not responding - error #241

Closed
johnsisland opened this issue Sep 12, 2016 · 12 comments
Closed

Refinery not responding - error #241

johnsisland opened this issue Sep 12, 2016 · 12 comments
Assignees
Labels
Milestone

Comments

@johnsisland
Copy link
Collaborator

I am trying to update a "hidden" listing record before making it LIVE today. Upon trying to "save", it hung up for about 1 minute, then generated this error attached (Sorry but something went wrong).

All I did was update the text/body copy, and added a floor plan file. BTW, Refinery frequently takes a while to initially load upon logging in for the first time

screen shot 2016-09-12 at 11 10 05 am

.
@CodySwannGT
Copy link
Member

The dashboard?

https://www.dropbox.com/s/v7xlbz05gx1toqc/Screenshot%202016-09-12%2011.17.12.png?dl=0

On Mon, Sep 12, 2016 at 11:15 AM, johnsisland notifications@github.com
wrote:

Assigned #241 #241 to
@CodySwannGT https://github.com/CodySwannGT.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#241 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAR4O-CThChdwH3K5XK5ReaFL38hwdjMks5qpWypgaJpZM4J6stj
.

Cody Swann - CEO, Gunner Technology
T: 213.915.4083 | cody@gunnertech.com | www.gunnertech.com
http://www.gunnertech.com/Skype: cody.swann

CONFIDENTIALITY NOTICE: This email message, together with any documents,
files and/or email messages attached to it, is intended for the sole use of
the individual or entity to whom it is addressed, and may contain
information that is legally privileged, confidential and restricted from
disclosure. If you are not the intended recipient, or responsible for
delivery to that person, you are hereby notified that any dissemination or
copying of this communication is STRICTLY PROHIBITED. In such case please
notify the sender by reply email and delete this message without reading,
printing or saving.

@CodySwannGT
Copy link
Member

Oh sorry. I only got the assigned message

@johnsisland
Copy link
Collaborator Author

johnsisland commented Sep 12, 2016

I just tested something. I ONLY changed field information and saved. It works. When I try to upload the floor plan PDF...it doesn't work...times out and generates the error. We seem to have issues with uploading files?

Here's the PDF I'm trying to attach.
255Llwyds_FLOOR.pdf

@johnsisland
Copy link
Collaborator Author

@CodySwannGT
Copy link
Member

The PDF was gigantic (600+k) and uncompressed, so the servers were timing out (And they're set at maximum timeout), so I compressed the pdf and reuploaded it (200+k) and it saved just fine

@CodySwannGT CodySwannGT added this to the September milestone Sep 12, 2016
@johnsisland
Copy link
Collaborator Author

That's well under 1 MB. All of our floor plans are under 1 MB and we never have issues. This doesn't make sense. Plus it's showing as a reverse image (black paper with white lines). I think it has something to do with the way the PDF was saved and not the file size.

I'm deleting it now and will try different optimized PDFs.

@johnsisland
Copy link
Collaborator Author

Here's a typical floor plan PDF file size (689 KB) and we never have issues. The 255 Llwyd's floor plan came directly from an architect, so I think it has something to do with the way it was saved as a PDF.

@CodySwannGT
Copy link
Member

Maybe. I just did a standard export via preview with a file size
compression and it went off without a hitch. So it could have been a
corrupt file - or maybe there was a lot of unnecessary embedded data which
was delaying it? Not sure, but those PDFs shouldn't be anywhere near 600k
anyway, so it's good that we caught that now.

On Mon, Sep 12, 2016 at 11:36 AM, johnsisland notifications@github.com
wrote:

Here's a typical floor plan PDF file size (689 KB) and we never have
issues. The 255 Llwyd's floor plan came directly from an architect, so I
think it has something to do with the way it was saved as a PDF.


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#241 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAR4O2AXrKFdpVuaRqslpyxr6jSpUtdGks5qpXFzgaJpZM4J6stj
.

Cody Swann - CEO, Gunner Technology
T: 213.915.4083 | cody@gunnertech.com | www.gunnertech.com
http://www.gunnertech.com/Skype: cody.swann

CONFIDENTIALITY NOTICE: This email message, together with any documents,
files and/or email messages attached to it, is intended for the sole use of
the individual or entity to whom it is addressed, and may contain
information that is legally privileged, confidential and restricted from
disclosure. If you are not the intended recipient, or responsible for
delivery to that person, you are hereby notified that any dissemination or
copying of this communication is STRICTLY PROHIBITED. In such case please
notify the sender by reply email and delete this message without reading,
printing or saving.

@johnsisland
Copy link
Collaborator Author

Its this closed b/c we've determined it's not a size limitation and a bad PDF? What is the size limitation anyway? Ive never had issues with uploading a floor plan file under 1 MB.

@CodySwannGT
Copy link
Member

It's closed because I fixed the issue by compressing the PDF and uploading
it.

There is no file size limitation - there's a server timeout of 30 seconds.
So if any process takes longer than 30 seconds, the server will kill it so
the rest of the site doesn't go down. In the terms of PDFs, the app does
quite a bit of processing on newly uploaded PDFs - some of that time is
dependent on the size - some of that may be dependent on how the file was
saved.

On Mon, Sep 12, 2016 at 11:45 AM, johnsisland notifications@github.com
wrote:

Its this closed b/c we've determined it's not a size limitation and a bad
PDF? What is the size limitation anyway? Ive never had issues with
uploading a floor plan file under 1 MB.


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#241 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAR4O2Wlg_3L1Xp_MO0OSFVV9FTS3IRNks5qpXOrgaJpZM4J6stj
.

Cody Swann - CEO, Gunner Technology
T: 213.915.4083 | cody@gunnertech.com | www.gunnertech.com
http://www.gunnertech.com/Skype: cody.swann

CONFIDENTIALITY NOTICE: This email message, together with any documents,
files and/or email messages attached to it, is intended for the sole use of
the individual or entity to whom it is addressed, and may contain
information that is legally privileged, confidential and restricted from
disclosure. If you are not the intended recipient, or responsible for
delivery to that person, you are hereby notified that any dissemination or
copying of this communication is STRICTLY PROHIBITED. In such case please
notify the sender by reply email and delete this message without reading,
printing or saving.

@johnsisland
Copy link
Collaborator Author

johnsisland commented Sep 12, 2016 via email

@johnsisland
Copy link
Collaborator Author

There is something wrong with the way the PDF was originally created as we're getting the inverse effect. We've posted about that before in the past and I found it was the way the PDF was created. It has something to do with the "optimize for fast web view" or a "thumbnail" option. In the past, I had fixed this undesirable inverse effect by "unchecking" the Optimize for Fast Web View...however, in this scenario, nothing helped. So it's how the architect originally saved the PDF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants